Xpediter is a powerful tool for debugging and testing COBOL programs in a CICS environment. It allows you to set breakpoints, monitor variables, change data, and execute code interactively. In this article, you will learn how to use Xpediter to debug COBOL programs in a CICS environment in six steps.
Before you can use Xpediter to debug your COBOL program, you need to prepare it by compiling it with the Xpediter option and linking it with the Xpediter stub. This will enable Xpediter to access the program's source code, symbol table, and logic flow. You also need to ensure that the program is registered in the CICS program definition table (PDT) and that the Xpediter terminal is defined in the CICS terminal control table (TCT).
Ensure your CICS region is configured to use Xpediter. This involves setting up the required libraries and configuration files. Start a debugging session by entering the appropriate Xpediter transaction code (usually XPED or XPRT) in your CICS terminal. Please consider below setup to be done for using Xpediter for a Cobol-CICS: Define & Install Map, Program, Trans id to make entries into PCT, PPT control tables. FCT and RCT control tables needs to entry of file & DB2 Plan.
Compile your CICS program with right compile parameters suitable for online with debug mode enabled. Then in CICS region, you can new copy it using CEMT command as follows, CEMT SET PROG(PGMNAME) NEWC PGMNAME will be your program name. When we do this, then the required CICS tables will be registered with the debug enabled program.
You can run Xpediter for batch programs. Prepare your program compiling with the Xpediter stub. You will need to prepare a JCL to run your program, adding one parameter for Xpediter control.
To start the Xpediter session, you need to sign on to the Xpediter terminal and enter the command XPED. This will display the Xpediter main menu, where you can select the option to debug a CICS program. You will then be prompted to enter the name of the program and the transaction ID that will invoke it. You can also specify other parameters, such as the mode (single or multi-user), the session ID, and the source library.
Starting an Xpediter session is straightforward, but it's essential to ensure that all necessary parameters are correctly specified to avoid session errors. While entering the program name and transaction ID is crucial, don't overlook the importance of correctly setting the mode (Single or Multi user) and source library. These settings can significantly impact the debugging process, especially in multi-user environments where session conflicts might occur.
To run batch programas inside TSO, find "Compuware", then Xpediter/Tso, then option 2 - Debug Programs interactively under TSO.
Invoke the xpeditor by giving the command XPED. Then invoke the source code by typing the program name. There we get the compiled source code with the complete listing with all the copybooks in expanded state. This source will be ready for debugging when we hit the programs
Once you have entered the program and transaction information, Xpediter will display the source code of the program on the screen. You can then set breakpoints by entering a B in the command column next to the line number where you want to stop the execution. You can also set conditional breakpoints, watchpoints, and tracepoints by using different commands. You can also change the display options, such as the number of lines, the format, and the colors, by using the PF keys.
When your JCL starts, Xpediter will display the source code same way as described for CICS. You can run your programs in the same way as described for CICS. Once inside Xpediter, the interface and commands are similar, both for CICS and TSO.
Set breakpoints by specifying the line number or condition where you want the execution to pause. This allows you to inspect the state of the program at critical points. Use watchpoints to monitor changes to specific variables, helping you identify where and why unexpected values occur.
After setting the breakpoints and options, you can execute the transaction by entering the command EXEC or pressing the PF4 key. This will initiate the CICS transaction and run the program until it reaches a breakpoint or completes normally. You can then view the values of the variables, the contents of the files, and the messages in the CICS system log. You can also change the values of the variables or files by entering a C in the command column and typing the new value.
In the batch environment, Xpediter works in a similar way to CICS. You can view and/or modify variable values, and use the same function keys.
In Online program debugging, you can use commands like 'K Var Name' in the command line to keep the value of a varibale. 'WHEN Var Name Changes' or 'WHEN var-name= 'value'' some more commands to check the variables value.
To step through the code, you can use the PF keys to perform different actions, such as stepping over a line, stepping into a paragraph or section, stepping out of a paragraph or section, or continuing to the next breakpoint. You can also execute a specific line of code by entering an E in the command column and pressing the ENTER key. You can also view the logic flow of the program by entering an L in the command column and pressing the PF11 key.
You will work the same way in tso with your batch program. In both environments, be careful with COBOL/DB2 programs. DB2 inserts a giant paragraph of DB2 statements immediately after the PROCEDURE DIVISION. The first time your program encounters a DB2 statement (a SELECT for example), if you press "F9" the flow will be diverted to this paragraph that has a hundred lines. So you don't waste time, mark a breakpoint on the line immediately following SELECT. When you reach the select line, press "PF12".
You also use GOTO command to pass the control on specific statement or paragraph, but this is not recommended. You need to keep the break points at different places in the code.
To end the Xpediter session, you can enter the command END or press the PF3 key. This will terminate the CICS transaction and return to the Xpediter main menu. You can then sign off from the Xpediter terminal by entering the command SOFF or pressing the PF12 key. You can also save your breakpoints, options, and session parameters by entering the command SAVE or pressing the PF10 key.
From the main Xpediter menu, use the PF3 (Function Key 3) key or type EXIT to leave Xpediter and return to the CICS terminal screen. If you are in a nested menu or command screen within Xpediter, you might need to press PF3 multiple times to back out to the main menu and then exit. Also if you are done with your work on CICS region, then it is good practise to log off from the CICS region using CESF LOGOFF command.
U need a catalog file to use xpeditor in cics or batch this as to be created and enabled at the compile time. It's depends on the SCM versions tools. It will be one time activity. To add xpeditor if someone using the program in debugging the other person cannot load the changes in the same environment. Then there is option in cics to force load the program.