debug problem

stly · New User Joined: 25 Jul 2005 Posts: 93

hi guys and gals
can any one explain

how to debug a program with out using XPEDITER?

till now i hav worked with tool.so please clarify me.

notonly4u · New User Joined: 26 Apr 2005 Posts: 87 Location: Hyderabad

Dear STLY,

The Program that yu are trying to debug is Batch Or Online?

If it is Batch.... Try to debug by using display statements. No other go as per my knowledge. Correct me If Iam wrong.

Regards
Tanden

vijayamadhuri · Active User Joined: 06 Apr 2005 Posts: 180

The other option is intertest.

stly · New User Joined: 25 Jul 2005 Posts: 93

hi vijay
u r so naughty man.thank u 4 uy smily reply.actually wat i mean is with out using tools how to debug.

hi notonly
u r right n thank u 4 ur reply. i too got that it cab b done using display.can i hav a simple code with example so that i will hav the clear picture.

notonly4u · New User Joined: 26 Apr 2005 Posts: 87 Location: Hyderabad

Hi Stly,

If you are doing some batch testing yu can use display statements in order to know the values that yu got after execution of certain logics.

Suppose you are accessing a Table for some records, If the search is sucessfull, you need to moveout and go for someother paragraphs. Else if not sucessfull, you have to go for searching a series of other tables. So after each search, you can make a display statement and yu can verify from the spool that which table contains your set of records.

If you are still not clear, please let me know, I'll try to explain that to you with a better example.

Thanks and Regards
Tanden

stly · New User Joined: 25 Jul 2005 Posts: 93

hi notonly
tq very much i got it but can i hav the example so that it will b more clear bcoz i havn,t worked on that till now.thanks once again 4 ur patience replies.

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

Hi Stly,

The 1st thing you should do is compile your pgm w/the nooff,list options. You can do this by coding PROCESS LIST,NOOFF on a line before your IDENTIFICATION DIVISION stmt. What this does is print a listing of the assembler language stmts generated by the compiler for the cobol stmts you coded. This listing shows all the cobol verbs coded and the assembler isnstructions it generated and their offsets into the pgm.

When an abend occurs the sysmsg for the job will contain the offset into the cobol pgm where the abend occured. You use that offset in the cobol listing to find the assembler instr that caused the abend.

On a line above that instr will be the associated cobol verb. Depending on the nature of the abend you can use this info to solve the problem. For example if the abend ic an 0C7 you can find the fields in the arith stmt that have bad data in the dump.

If you don't know how to do that you can display the fields just before the offending cobol stmt is executed.

stly · New User Joined: 25 Jul 2005 Posts: 93

hi notonly, mmwife n all thank u very much 4 ur answers.thans to one and all

stly · New User Joined: 25 Jul 2005 Posts: 93

hi notonly, mmwife n all thank u very much 4 ur answers.thans to one and all

stly · New User Joined: 25 Jul 2005 Posts: 93

hi notonly, mmwife n all thank u very much 4 ur answers.thans to one and all