Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Debugging Functions

This section discusses how to test load modules that consist of multiple programs or control sections (CSECTs). The sections of the section show how to access source code and set breakpoints in calling and called programs, execute a program with multiple CSECTs, and return to the calling program. It also provides ways to select and exclude CSECTs.

Many modules consist of individual source members that are compiled or assembled separately, then link-edited together to create a load module. Code Debug CICS lets you debug these CSECTs at the source level, even when the CSECT is not defined in your program resources.

The automatic CSECT support facility provides screens that list the CSECTs associated with each program. You choose the program for which you need to see the source. Facilities are also available so that IBM or vendor-supplied CSECTs may be excluded from automatic CSECT processing.

In this section, you will set a breakpoint in the calling program CWDEMC, then access the source code for CWLESUBA and set a breakpoint there. CWLESUBA is a subroutine linked into CWDEMC that does not have an entry in the program resources to define it to CICS. After setting the breakpoint, you will execute the transaction that runs CWDEMC and step through the source in CWLESUBA.

Important

If you cannot obtain a source listing for CWLESUBA, your site may not be licensed for Assembler support. When the NO SOURCE AVAILABLE message appears, press PF1 for source information. If your site is not licensed for Assembler support, you can use the information presented in the previous section, Debugging Applications Without Source Code, to create a pseudo-listing for CWLESUBA.

The demonstrations in this section should be performed in Code Debug’s standard operating mode — not one of the three restricted modes. For more information, see the Code Debug CICS Reference Manual.

DLL modules are supported at the CSECT level on the 2.6.1 screen described later in this section. DLL modules are also supported at the function level via the 2.6.F screen. If you are debugging a DLL module containing multiple functions, see to the Code Debug CICS Reference Manual for further details.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*