Accessing Code Debug CICS

To access the appropriate transaction, type XPED, XPRT, or XPSP on a blank CICS screen and press Enter.

Use the following transaction format to access a function directly:

module:csect

If you want to set breakpoints or keeps via source, you can enter the XPED, XPRT, or XPSP transaction code followed by one space and the load module name. You can also specify a load module and CSECT combination separated by a colon (:). This transfers you directly to the 2.L (Source Listing) screen and displays the source for the module name entered, as well as the desired CSECT, if specified. You can then immediately set breakpoints or keeps.

You can also specify a particular screen ID, with or without a module or module:CSECT combination, and go directly to the desired function, all in one step. Enter the XPED, XPRT, or XPSP transaction code followed by one space, and then enter the desired screen ID. For example, entering either XPED 2.2, XPRT 2.2, or XPSP 2.2 will take you directly to the Memory Display screen (2.2). Parameters can be specified in any sequence, so entering either XPED CWDEMCB2 2.2 or XPED 2.2 CWDEMCB2 will load program CWDEMCB2 and display its load module storage on the Memory Display screen (2.2). Entering XPED CWDEMCB2:CWCDSUBA 2.2 will load program CWDEMCB2, select the CSECT named CWCDSUBA, and display the storage for the module and CSECT on the Memory Display screen (2.2).

profile-name

You can specify a profile to use with the XPED, XPRT, or XPSP session. For more information, see Establishing-a-Profile.

script-name

A user or system script can also be specified to execute at session initialization. For more information, see INCLUDE (INC).

sysidnt/applid/trans

If Code Debug’s support for CPSM Dynamic Transaction Routing is configured, the routing decision can be influenced by specifying one of these parameters. For more information, see Code Debug Transaction Routing.

Accessing the XPED and XPRT Transactions

You can access the XPED or XPRT transaction level functions either through the Primary Menu or directly by specifying the corresponding screen ID, for example 2.L for the Source Listing screen.

The Primary Menu shows the name and screen number for each functional area in XPED/XPRT. Use this screen to transfer to a functional area or to enter a program name for setting breakpoints and/or keeps before returning to CICS.

Primary Menu (XPED/XPRT)

To access a menu for an XPED/XPRT function, type the screen number for that menu in the COMMAND field and press Enter. The menu lists the screens available for that function. The following menus are available from the Primary Menu:

Session Profile (0): Establishes default values used during a Code Debug CICS session.

Session Control (1): Provides options for controlling the Code Debug CICS session.

Debugging Facilities (2): Provides options for interactively debugging application programs.

File Utility (5): Displays and updates CICS data sets, temporary storage queues, transient data queues, and DL/I databases. Also lists and browses MQ queues.

Abend-AID for CICS (7): Accesses the Abend-AID for CICS product if it is installed and active on your system.

Code Coverage (C): Provides an interface to the Code Coverage product if it is installed and active on your system.

Xchange/CICS (G): Provides an interface to the Xchange product if it is installed and active on your system.

CICSPlex Facilities (P): Accesses CICSPlex control facilities if they are installed and active on your system.

Exit (X): Ends a debugging session or requests a dump.

To use the XPED/XPRT level:

1. Type XPED or XPRT on a blank CICS screen and press Enter. The Primary Menu is displayed as shown in Primary Menu (XPED/XPRT). Code Debug CICS automatically sets transaction abend trapping unless the default for trap has been changed to OFF.
2. Type 1.6 in the COMMAND field to access the Trap Summary screen (1.6) and set an abend trap. (Alternatively, the SET TRAP ON command provides the same functions.)
3. Type 1.4 in the COMMAND field to access the Trace Summary screen (1.4) and set the trace facility on. (Alternatively, the SET TRACE ON command provides the same functions.)
4. Type 1.8 in the COMMAND field to access the Storage Protection screen (1.8) and set storage protection options. (Alternatively, the SET PROTECT ON command provides the same basic function but for store protection only.)
5. Execute the transaction or identify a program in which to set breakpoints.
   • If you are not setting breakpoints, press Clear to return to CICS, then enter the transaction code of the application you are testing. If an abend occurs, Code Debug CICS automatically displays the Source Listing screen (2.L).
   • To stop the program at a specific statement, or to display specific data names at an abend, type the program name and =2.L to display the Source Listing screen (2.L). Set your breakpoints, then press Clear to display a blank screen. Enter your test transaction.

Accessing the XPSP Transaction

You can access XPSP transaction level functions either through the Primary Menu or directly by specifying the corresponding screen ID.

The XPSP Primary Menu is identical to the XPED/XPRT menu except for the system facilities area that is available to XPSP users. This Primary Menu shows the name and screen number for each available function menu. Use it to transfer to another system area.

Primary Menu (XPSP)

1. Type XPSP on a blank CICS screen and press Enter. The Primary Menu is displayed (see Primary Menu (XPSP)). Code Debug CICS is ready for system programming functions or transaction debugging.
2. Type 9.6 in the COMMAND field to access the Trap Summary screen (9.6) and set an abend trap. (Alternatively, the SET TRAP ON command provides the same functions.)
3. Type 1.4 in the COMMAND field to access the Trace Summary screen (1.4) and set the trace facility on. (Alternatively, the SET TRACE ON command provides the same functions.)
4. Type 9.8 in the COMMAND field to access the Storage Protection screen (9.8) and set storage protection options. (Alternatively, the SET PROTECT ON command provides the same basic function, but for store protection only.)

Selecting Functions from Menus 

You can access all Code Debug CICS functions through the menu system. Each menu lists the primary functions for that level and contains submenus that list all the functions related to that topic. To select a function from a menu:

• Type the number or letter associated with the desired screen in the COMMAND line and press Enter.
• Position the cursor next to the desired function, type an S, and press Enter.
• Position the cursor anywhere within the description of the desired function and press the PF key to which the SELECT command has been assigned (default PF15).
• Enter the SELECT command in the COMMAND line, position the cursor anywhere within the description of the desired function, and press Enter.

Transferring Between Screens 

Because Code Debug CICS is based on a menu structure much like that of ISPF/PDF, you can transfer from one screen to another in several ways:

• To transfer from the Source Listing screen (2.L) to one of the Program Storage screens (2.3) for example, type =2.3 from the 2.L screen and press Enter.
• To transfer from the Program Trace screen (2.4) to the Session Control Menu (1) for example, type =1 from the 2.4 screen and press Enter.
• To transfer to the Exit Session screen, type =X.