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.

Exiting Code Debug CICS and ending the debugging session (Code Debug CICS COBOL)

Related Topics

Quick Reference

Overview

Debugging-Db2-Program

All of the breakpoints, skips, counts, and keeps you set are associated with your terminal. When you finish testing, it is very important that you end your debugging session. This frees up any resources that may have been used during the session (including abend traps which intercept programs when they abend) and releases all breakpoints, keeps, skips, and counts from your programs.

Ending a session

  1. Type =X in the COMMAND field on any Code Debug CICS screen. If you are not currently in Code Debug CICS, type XPED X on a blank CICS screen. Press Enter. The Exit Session screen (X) appears.

    Exit Session Screen (X)

     ---------------------------------- EXIT SESSION (X) --------------------C024
    COMMAND ===>
    MODULE:          CSECT:

    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: YES      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: 000
    PROTECTION ENTRIES:   000
    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.
  2. Type Y (for YES) in the END SESSION field.
  3. If you had trapped a transaction and would like a dump, type Y in the DUMP OPTION field.
  4. If you would like to execute a user or system script, type the script member name in the POST SCRIPT field.
  5. Press Enter. Code Debug CICS displays the message Code Debug CICS SESSION TERMINATED - SYSID=C123 to show that any resources used during the debugging session are released.

You may also exit Code Debug directly, bypassing the Exit Session screen (X), by typing XPND on a blank CICS screen.

The Resource Summary screen (1.P) can be used to release breakpoints set from the local terminal, and the XPSP transaction’s Resource Summary screen (9.P) can be used to release breakpoints from programs in the entire CICS region. This is especially helpful if your site uses autoinstall terminals and you sign off CICS without ending an Code Debug CICS session. For more information, see the screen descriptions for the Resource Summary screens (1.P and 9.P) in the Code Debug CICS Reference Manual.

 

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