Debug View for CICS
The Debug view provides information about the debug session and controls for forwarding progress of the debug session. The Debug view gives information about the call path that execution has followed to the current location. The information, which is derived from the call stack using a methodology that depends on standard z/OS linkage conventions, may include CSECT, load module, label, line number, address, and offset. If the information presented does not appear accurate, ensure that standard z/OS linkage conventions were followed.
Debug View Options
Button | Description |
|---|---|
Varies | The launch configuration used to launch the current debug session. Along with an icon that varies, the name of the configuration along with the type of the configuration (such as Xpediter CICS Debug Session) appear in name [type] format. |
| The CICS region chosen in the launch configuration. The debug session is currently connected to this region. |
| The thread of execution and the current status of your debug session. The thread label displays the task number, initiating transaction, and the terminal from which it originated. |
| A stack frame representing a called routine/program within execution. The call stack is presented in chronological order, with the current stack frame on top and the least recently called stack on the bottom. As much information as possible is given for each stack frame. The top stack frame displays the current line number that execution is at. If a line number is shown for any other stack frame, it is the line number that a call was made within that given stack frame. Important To show IBM system modules in the call stack, in the Debug view, click |
, then select Xpediter>Show System Modules. Alternatively, from the Xpediter Preferences page, select the Show system modules in the call stack check box. By default, system modules are not shown.Debug View Toolbar
Xpediter/Eclipse provides debugging controls in the Debug toolbar. Each control is enabled depending on which item is selected in the Debug view.
Button | Description |
|---|---|
| Remove all Terminated Launches -Click to clear out all terminated launches from the Debug view. It is only enabled when terminated launches exist in the Debug view. |
| Resume - Click to continue execution. This button is only enabled when a system, thread, or stack frame item is selected and program execution is suspended. |
| Terminate** - Click to end your debug session. This button is enabled for any item selected but is disabled for terminated sessions. Clicking this button when a thread or stack frame is selected stops execution of your program, but does not end your session. Clicking this button when a region or configuration is selected ends your session. |
| Step Into - Click to step into the call and step line-by-line through it. When execution is stopped at a CALL statement, Step Into places the execution pointer at the first statement within the CALL. When execution is stopped at a non-CALL statement, Step Into performs a Step Over. |
| Step Over - Click to execute the call but not step line-by-line through it. If the program is suspended on a COBOL PERFORM paragraph/section, clicking this button will cause the paragraph/section to be executed but not stepped through line-by-line. If a breakpoint is encountered or an abend occurs before execution reaches the return point, execution stops at that breakpoint/abend instead. This button is only enabled when a thread or stack frame item is selected and program execution is suspended. |
| Step Return - Click to return to the program that invoked the current program and place the execution pointer at the next available statement after the calling sequence. If a breakpoint is encountered or an abend occurs before execution reaches the return point, execution stops at that breakpoint/abend instead. If there is no calling program in the current context, performing a Step Return ends the debug session. |
| Review Step Backward - Directs Xpediter to go 1 step backward. |
| Review Step Forward - Directs Xpediter to go 1 step forward. |
| Review Resume Backward - Directs Xpediter to go backward to the next breakpoint or to the point where monitoring started. |
| Review Resume Forward - Directs Xpediter to go forward to the next breakpoint or to the current line of execution. |
| Exit with Abend - Click to request that the step terminate with a particular abend code. Specifying Unnnn causes a USER ABEND nnnn code to be used, while specifying Snnn causes a SYSTEM ABEND nnn code to be used. |
| View Abend-AID Report - Click to display an Abend-AID Snapshot report containing context-sensitive diagnostic information about an abend. If no abend is present, the Snapshot report displays environment-specific run-time characteristics during a test session. If you have the Abend-AID VSAM, IDMS, IMS, or DB2 options, the report also displays subsystem-related debugging information. |
Clicking 
when a thread or stack frame is selected ends program execution, but not the session. When a program runs to completion, the program’s associated transaction can be reentered to run again and Xpediter/Eclipse traps it. You can also display source for a different program using the Open DDIO view, set a breakpoint at the first line of execution, and then cause that program’s associated transaction to be executed, providing an opportunity to debug a different program within the same debug session. Refer to the Breakpoints-and-the-Breakpoints-View and the Open-DDIO-View topics for more information.
For more information, see Monitoring and reviewing the execution path.