Finding the Bad record in a file which caused the abend

harikiran2001 · New User Joined: 02 Jan 2008 Posts: 4 Location: bang

Hello All,

Can any one please tell me how to find the bad record in a file, which is the cause for the job to abend. I want a solution ,something like i can find it in the abend aid.

Something like a the record number or something displayed in abendaid , with which i can strip off and rerun the job.

Yours help is greatly appreciated.

Thanks in advance,
Harikiran

socker_dad · Posted: Fri Jan 04, 2008 1:08 am

Well.......

No such utility I know exists. All you can do is hard work.

Was your job writing an output file? Then find the last good record written and start from there on your input file.

Was it an master file update program? Unless you are keeping some sort of program-internal checkpoints, you're screwed.

Was it a DB2 application with commit and rollback logic? Then you have other diagnosis opportunities.

Alas, all of these require effort on your part.

Phrzby Phil · Posted: Fri Jan 04, 2008 1:39 am

Should you be creating a corresponding output file (could be print), note that if it is not single-buffered, then the last record written will not correspond to the last input record properly processed.

Soccer's last point is important to many quesitons posed on this website - sometimes you must do it yourself. Study the program well enough to know where to put in some tracing. If you trace conditionally, then you can turn it off by setting the condition variable and leave the trace code in the program.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

I always put read/write counters in my pgms for this and other reasons. Though I display them at EOJ, at abend the cntrs cotain the rec cnts at that time.

If you don't know how to find them in a dump, put "cntrs*start"/"cntrs*end" literals before and after them in WS.

rakesh17684 · New User Joined: 08 Oct 2006 Posts: 61 Location: San Diego

Get the records into an Excel sheet and try analysing with the sheet or u can try out to get that records using some file processing lang( like easytrieve,etc.,.)
Hope it helps

stodolas · Posted: Tue Jan 08, 2008 6:11 pm

Excel can't handle most files. It only holds 65000 rows. Why move the data to a PC when there are similar tools you can use on the mainframe?

Phrzby Phil · Posted: Tue Jan 08, 2008 6:25 pm

I believe that Vista Excel allows at least double the 65K rows, but the point is the same - this is not a "dump to Excel" solution.

Jack - I like your approach - great idea.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

Thanx Phil.

stodolas · Posted: Wed Jan 09, 2008 4:50 am

Someone at our site wrote an Eztrieve that runs through a file checking for bad lengths.