Compilation/syntax errors are easy to detect - as outlined above by narender. For run time (execution time) errors, you need to do what is known as dump reading. Generally most programs abend with register dumps (hexadecimal) and for small programs it is easy to calculate the offset of the offending instruction by inspecting the Aseembler Gen.
For large complex programs, use IPCS and the debugging handbooks to locate and interpret major MVS control blocks in a dump. In other words you have to trace the os blocks as mapped by IBM macros. Please see the IBM classic manuals "MVS Debugging handbooks". They are a great reference material for IBM Assembler. Unfortunately these books are IBM Licensed products (Lxxx-xxxx numbers) and are usually available to mainframe customers. Your work (employer) may have these collections.
ok Pelad, i will check in my shop...anywz thanks for ur kind reply...if u have any reading materials on this topic, if you don't mind can u PM me..it will be great help for me..
thanks in advance
Look at "OS/390 elements and features Adobe? Acrobat? PDFs" section below on page and Select your OS version - for eg. V2R6
- BookManager book
- Product bookshelf
- OS/390 elements and features messages and codes
[ V2R10 | V2R9 | V2R8 | V2R7 | V2R6 | V2R5 | V2R4 | V1R3 | V1R2 | V1R1 ]
- OS/390 elements and features Adobe? Acrobat? PDFs
[ V2R10 | V2R9 | V2R8 | V2R7 | V2R6 | V2R5 ]
- OS/390 software products Adobe Acrobat PDFs
- Other available Adobe Acrobat PDFs
[ Hardware | VSE | z/OS | z/OS software | z/VM ]
For Debugging the assembler code you can use the following tools.
1. Tracemaster: If you want to debugg your code line by line basis for better understanding, then this utility is best.
I am giving you a PPT regarding assembler debugging.
2. Dumpmaster: This utility are used for solving abends. If any program gives some abends. In the command line write DM to start the Dumpmaster. In the spool u will get a file a called dumfile. As you code in your JCL as DDNAME SYSABEND OR SYSUDUMP. Give that file in the DM and it will show all the details. Which instruction is causing that abend. What are the values stored in that moment in the respective variables. Now from there u can pick up the offset value and go to the compiler listing of the program and get the instruction also.