MVSFORUMS.com

nagendra_gv · Posted: Mon Feb 02, 2004 6:50 am Post subject: Control Records

HI,

how do i find in a particular cobol program that where the records r getting dropped excluding cclibs(i mean excluding the drop,sort,include).

kolusu · Posted: Mon Feb 02, 2004 9:09 am Post subject:

Nagendra,

Hmm I am not really sure if I understood your question. You have a program and you want to know why some records are being dropped?

What has cclibs( assuming you meant copylibs), include got to do with dropping the records?

I haven't come across a DROP verb in cobol.

Records can be dropped in a sort procedure (duplicates , include cond , omit cond).

Please post as much information as you can. This will avoid unnecessary guesswork and helps in getting a better response.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

nagendra_gv · Posted: Tue Feb 03, 2004 12:54 am Post subject:

cclibs mean control card library,as u said we can find Records can be dropped in a sort procedure (duplicates , include cond , omit cond). But how can i find in a normal cobol program where the records r dropped(plain cobol) don't even look into the jcl

kolusu · Posted: Tue Feb 03, 2004 6:30 am Post subject:

nagendra_gv,

Understand the program logic. One easy way to do it is start tracking backwards from the write statement of the file. Note all the places where the output file is written and determine the logic for dropped records.

Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

kok328 · Posted: Fri Feb 13, 2004 12:07 pm Post subject:

I'd take a unique and unmodified part of the record and save it off into working storage. The upon the write statement, compare the working storage field to the same part of the record your writing. If these two fields differ, your not writing the same record you read. When this occurs, display the working storage field and then go back into the program using Expediter...set a break on the read statement for the value in the display statement and then follow the record thru the code until it drops (goes back to read not write).