How to debug a simple cobol program using xpeditor?

In this Mainframe Forum - You can post your queries on XPEDITER tool

Moderator: Moderator Group

Post Reply
anilsani285
Member
Posts: 10
Joined: Sun Jul 04, 2010 5:26 pm

How to debug a simple cobol program using xpeditor?

Post by anilsani285 » Sun Jul 04, 2010 5:35 pm

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
Anil-Sani

User avatar
dbzTHEdinosauer
Moderator
Posts: 981
Joined: Mon Oct 02, 2006 8:31 pm

Post by dbzTHEdinosauer » Sun Jul 04, 2010 6:20 pm

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.
Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

anilsani285
Member
Posts: 10
Joined: Sun Jul 04, 2010 5:26 pm

Post by anilsani285 » Sun Jul 04, 2010 6:50 pm

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.
Anil-Sani

User avatar
dbzTHEdinosauer
Moderator
Posts: 981
Joined: Mon Oct 02, 2006 8:31 pm

Post by dbzTHEdinosauer » Sun Jul 04, 2010 7:40 pm

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.
Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

User avatar
Natarajan
Moderator
Posts: 537
Joined: Fri Oct 10, 2008 12:57 pm
Location: chennai
Contact:

Post by Natarajan » Sun Jul 04, 2010 9:11 pm

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
Natarajan
Chennai

User avatar
dbzTHEdinosauer
Moderator
Posts: 981
Joined: Mon Oct 02, 2006 8:31 pm

Post by dbzTHEdinosauer » Sun Jul 04, 2010 11:01 pm

in addition, when you receive your S0C7, you can look at memory and see what record is there, as well as the invalid data.
Dick Brenholtz
JCL, SQL and code in programs have an irritating habit of doing what you say,
not what you meant.

academyindia4

Topic deleted by Admin

Post by academyindia4 » Fri Jan 22, 2016 12:27 am

<< Content deleted By Admin >>

Post Reply

FREE TUTORIALS

Tutorials
Free tutorials from mainframegurukul
  • JCL Tutorial
    Covers all important JCL concepts.
  • Cobol Tutorial
    This tutorials covers all Cobol Topics from STRING to COMP-3.
  • DB2 Tutorial
    DB2 Tutorial focuses on DB2 COBOL Programming.
  • SORT Tutorial
    This Tutorial covers all important aspects of DFSORT with examples
  • CICS Tutorial
    This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Interview
Mainframe Interview questions



Other References
Mainframe Tools and others