Exiting Code Debug for CICS reference guide

Related topics

The Exit Session screen (X) is used to check the status of exit options before ending the Code Debug CICS test session. You can terminate the session and/or produce a CICS transaction dump.

To exit Code Debug CICS, do one of the following:

Access the Exit Session screen (X) by typing an X on the Code Debug CICS Primary Menu, =X on any Code Debug CICS screen, or typing XPED X from a cleared screen.
To use the END SESSION and DUMP OPTION default options shown in the following sample screen and return to CICS, leave the COMMAND field blank and press Enter or the Clear key.
To end a debugging session, type YES in the END SESSION field. Always use this method to shut down Code Debug CICS when you have completed a debugging session.

Exit Session Screen (X)

----------------------------- EXIT SESSION (X) ------------------------C024
COMMAND ===>
MODULE: CWDEMCB2 CSECT: CWDEMCB2          COMPILED: 28 MAY 2003 - 11.11.29

END SESSION: NO       YES terminates the session, cleans up resources, and
                      frees any waiting remote tasks. NO returns to CICS
                      and leaves Code Debug active.

DUMP OPTION: NO       YES forces a dump (or Abend-AID for CICS report) for
                      any active abends currently trapped by this terminal.
                      The site options for dump suppression have precedence.

POST SCRIPT:          Script to execute at session termination.

PROGRAMS WITH BREAKS: 001
PROTECTION ENTRIES:   001
ACTIVE ABEND TRAPS:   001 (Individual trap entries set by this terminal)
WAITING TASKS:        000 (Active remote traps that have not been processed)

Press ENTER to process options.

The input and output fields on the Exit Session screen (X) provide you with several options for terminating a Code Debug CICS session.

Input Fields

END SESSION

Specifies whether to end the Code Debug CICS session or to just return to CICS with the session active. Valid entries are:

NO: Returns to CICS, leaving Code Debug CICS active. The default is NO.

YES: Performs the following:

Ends the session and releases all programs for which you have set breakpoints or keeps.
Terminates remote traps waiting for a Code Debug CICS response and removes their breakpoints.
Cleans up resources and frees waiting remote terminals.
Gives control to CICS and turns off Code Debug CICS for your terminal.

DUMP OPTION

Specifies whether to force a dump for active abends or breakpoints currently trapped by this terminal. Valid entries are:

NO: Does not produce a dump. The default is NO.

YES: Produces a dump (or Abend-AID for CICS report) for the abend or breakpoint currently trapped by this terminal.

POST SCRIPT

Allows you to specify a user or system script to be run at session termination.

Output Fields

PROGRAMS WITH BREAKS

Number of programs still containing breakpoints. Review these breakpoints using the List Breakpoints screen (1.1) to see if they are needed for later testing. See Setting-and-Removing-Breakpoints. Release the breakpoints and/or the program if not needed.

PROTECTION ENTRIES

Number of storage protection entries added during the debugging session. Review these entries using the Storage Protection screen (1.8). Only auto and user entries are deleted when the session is ended. SYST-type entries are not deleted by ending a Code Debug CICS session.

ACTIVE ABEND TRAPS

Individual trap entries set by this terminal.

Important

Program trace, monitor, and abend trapping have defaults that are set for an XPED user when Code Debug CICS is installed.

WAITING TASKS

Active remote abends that have been trapped and have not been processed. The remote terminal is locked until the transaction is resumed or terminated.