How to debug a simple cobol program using xpeditor?

[anilsani285]

1. I want to know all the simple complicated commands that are required to debug a simple Cobol program.

2. how to debug the Cobol code in reverse order also

[dbzTHEdinosauer]

sorry,

I only know complicated simple commands that are required to debug complex cobol programs.

also, since the computer executes commands from start to finish, i have never been interested in running my cobol code in the opposite direction.

PF1 would be a good place to start, since you are obviously too lazy to look at manuals,
which will be at your site, as well as other documentation.

[anilsani285]

Thanks for the reply....
i am very new to this tool ... i had one more question ..

suppose i had program that reads a file(10000 records) and move the data to some other ws-item because of the bad data i got SOC7. but i want to know at what record this soc7 had been raised it using xpeditor tool.

[dbzTHEdinosauer]

but i want to know at what record this soc7 had been raised it using xpeditor tool.

wrong tool for the job.

use the verify statement of your sort product to determine which record contains the bad data.

Or, change your program to determine when you have non-numerics and display the bad record number as well as the data that is contained. This type of pseudo-proofing code is normally in a well written program if you know or fear that you have input data that is output from a poorly written sub-system.

you use xpeditor to debug program logic, not to find bad data in input files.

[Natarajan]

I agree with Dick comments.

To resolve S0C7 refer following...
http://www.mainframegurukul.com/ibmmain ... light=s0c7



For XPEDITER tutorial refer..
http://www.mainframetutorials.com/XPEDITER.html

[dbzTHEdinosauer]

in addition, when you receive your S0C7, you can look at memory and see what record is there, as well as the invalid data.

[academyindia4]

<< Content deleted By Admin >>