Shell Programming and Scripting

Yes, I always put the opening { on the if line.
On the other hand, a correct awk should also handle two lines ... But all the other code looks okay.

$0 is the current line.
NR is the line number.
BTW I also put this in one line:

Code:

} else {

I repeat (from my 1st posting in this thread:
I understand the English description of the processing that is going on. To help you with your problem, we need to see the exact Korn shell commands that are being used to run your awk script. Saying:
doesn't give us any way to evaluate what might be going wrong.

Sorry Don, but our Batch document doesn't provide us that much detail yet as it is being put together at the moment.

On anohter note, is there a command I can use in Unix that can tell me the first line's record length if I navigate to the source directory?

I tried wc -c <insert filename> but it gives me the TOTAL character counts.

Length of first line:

Code:

awk 'NR==1 {print length($0)}'

If nothing else is to be processed, immediate exit is faster

Code:

awk '{print length($0); exit}'

---------- Post updated at 04:23 PM ---------- Previous update was at 04:15 PM ----------

Don suspects you run your script by the wrong interpreter. I can hardly believe this since you provided logfile. But to be sure I agree you should show how you run it.

Hi SoloXX,
When I last posted on this thread, I hadn't seen the sample input that you posted in message #3 in this thread 1 or 2 minutes before I hit the Submit Reply button. Now that we know that you have no idea what is going on, let me make a few commnets based on what you have shown us. First using CODE tags instead of ICODE tags and reformatting your awk script, it looks like this:

Code:

BEGIN { good_count = 0
        bad_count = 0
        line_count = 0
}
NR == 1 {
        rec_count = substr($0, 15, 8)
        date_str = substr($0, 32, 10)

        print "Date in Header Record : " date_str
}
NR > 1 {line_count++
        if (length($0) == 710) {
                print $0 > GoodFile
                good_count++
        } else {
                print $0 > BadFile
                bad_count++
        }
}
END {   if(line_count == rec_count && bad_count==0) {
                print "********************************************"
                print "Count in header : " rec_count
                print "Count in file received : " line_count
                print " "
                print "Number of Good Records : " good_count
                print "Number of Bad Records : " bad_count
        } else {
                print "********************************************"
                print " PROBLEM WITH FILE SENT FROM SOURCE "
                print " "
                print "Count in header : " rec_count
                print "Count in file received : " line_count
                print " "
                print "Number of Good Records : " good_count
                print "Number of Bad Records : " bad_count
                exit 99
        }
}

You keep asking how to find out how many characters are in the first line of your input file, but (as shown by the lines marked in red) this awk script doesn't care what the length is for the first line. It is checking to see that the length of every line AFTER the first line contains 710 characters not counting the terminating <newline> character. It assumes that the first line in the file contains at least 43 characters, but does not verify that that is true.

If you don't know how this awk script is being run, how do you know it isn't working correctly???

The file you uploaded (First row of src file.txt) happens to have 712 characters in the 1st line (counting the trailing <carriage-return> and <newline> characters), but the second line is incomplete. Since the file you uploaded contained 1422 bytes (and only contained one <newline> character as the 712th character in the file), we have no idea how long the 2nd line in the file is. Since awk is only specified to work on text files, the behavior of this script is unspecified when given your uploaded file as input. On OS X, it yields:

Code:

Date in Header Record : 04/22/2013
********************************************
 PROBLEM WITH FILE SENT FROM SOURCE 
 
Count in header : 400133  
Count in file received : 1
 
Number of Good Records : 1
Number of Bad Records : 0

but if you add a <carriage-return> and a <newline> to the end of your uploaded file (matching what is at the end of the 1st line in the file), it yields:

Code:

Date in Header Record : 04/22/2013
********************************************
 PROBLEM WITH FILE SENT FROM SOURCE 
 
Count in header : 400133  
Count in file received : 1
 
Number of Good Records : 0
Number of Bad Records : 1

As I said all of this is based on lots of conjecture, but if you won't show us how the script is used, how the input file is massaged before feeding it to the script, and any other pertinent details that have been hidden by not showing us how this awk script is invoked; we can't make any concrete suggestions on what, if anything, might be wrong. Maybe the <carriage-return> characters in you input file are discarded before the input is fed into this awk script??? Maybe the only <carriage-return> in the input file is in the first line (where it will be ignored).???