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.

Product Architecture of Code Debug for CICS

Related topics

Installation and Configuration Guide

Advanced Configuration Guide

Quick Reference

Debugging-Functions

Code Debug CICS is designed to provide different levels of functionality.

The ISPF-like nature of Code Debug and its source-based approach make it immediately familiar. Yet it is powerful enough to meet your most complex debugging requirements. Code Debug CICS provides an efficient, non-intrusive architecture that can protect the CICS region from storage violations. It also offers complete CICS-specific debugging capabilities for both application and system programmers in the CICS environment.

Code Debug CICS supports applications written in Assembler, C, COBOL, or PL/I, plus a variety of other programming languages on a sourceless Assembler instruction-level basis.

 Code Debug’s unique multi-access design lets users access the product through their choice of three separate and securable debugging transactions:

  • XPED access causes  Code Debug to display the Source Listing screen (2.L) when an abend occurs or a breakpoint is encountered.
  • XPRT retains the feel of earlier releases by displaying the Break/Abend screen (2.1) at an abend or breakpoint.
  • XPSP access provides all the power of the XPED and XPRT transactions, plus additional system maintenance capabilities for the CICS specialist responsible for supporting the CICS region.

XPED is the standard transaction used by application programmers. All the commands and functions available with XPED can also be accessed through the XPRT transaction. With either transaction, Code Debug CICS provides:

  • Display-only access to CICS storage areas
  • Update capability for application transaction storage areas
  • Access to FCT or CEDA-defined files, transient data, temporary storage, IMS databases, Db2 tables, and MQ message queues.

The only real difference between the two transactions is that when a breakpoint is reached or an abend occurs, XPED displays the Source Listing screen (2.L), while XPRT displays the Break/Abend screen (2.1).

The XPSP transaction is designed for those system programmers authorized to update unprotected CICS tables and control areas. It permits unrestricted storage area updates and provides hung task analysis, along with other special region maintenance and debugging functions. XPSP allows you to establish and control system-wide storage protection.

 Code Debug can also be configured to operate in any of three restricted modes of operation:

  • Diagnosis Mode
  • Utilities Mode
  • Diagnosis/Utilities Mode.

These modes allow a site to tailor its  Code Debug implementation to suit the processing integrity and throughput requirements of its various CICS regions. In Diagnosis Mode, the user is prevented from modifying data or changing the sequence of program execution. In Utilities Mode, only the  Code Debug file utility, storage display facility, and source listing utility are accessible. Storage, databases, and files can be viewed and modified, but trap, trace, and monitor functions are unavailable. Diagnosis/Utilities Mode combines the restrictions of the other two modes. You can access  Code Debug’s file utility and source listing utility and view storage on the Memory Display (2.2 and 9.2) and DSECTs (2.D and 9.D) screens. A mode indicator message is displayed in the upper left-hand corner of all  Code Debug screens when the product is operating in one of the restricted modes. For more information see Restricted-Operating-Modes.

Important

All descriptions in this manual, unless otherwise noted, pertain to  Code Debug’s standard, non-restricted operating mode.

XPED and XPRT Transactions

The XPED transaction accesses all of Code Debug CICS’s functions for source-level testing and debugging of your application program. The XPRT transaction is intended for CICS application programmers who prefer the break/abend approach to testing and debugging that was used in earlier releases of Code Debug CICS. Both transactions provide the same enhanced debugging features and allow you to browse CICS storage areas. XPED and XPRT also let you specify storage protection options, abend traps, and trace options. You can customize your debugging session through profile options that you can store and use again. If an abend occurs, Code Debug CICS automatically displays either the Source Listing screen (2.L) for XPED users, or the Break/Abend screen (2.1) for XPRT users.

The Code Debug CICS Primary Menu, displayed in the following figure, lists the screen number and name of each product facility menu available via the XPED and XPRT transactions. The option shown for Code Coverage, a sophisticated and powerful tool used with Code Debug CICS to verify the thoroughness of testing, is only displayed if the separate Code Coverage product has been installed for the current CICS region. The option shown for Xchange/CICS is only displayed if Xchange is active in the CICS region. The option shown for CICSPlex facilities is only displayed if the DYNAMIC_TRANSACTION_ROUTING_SUPPORT global parameter is set to YES.

There are four main ways you can navigate through Code Debug CICS:

  • Type one of the screen numbers from a displayed menu in the COMMAND field and press Enter.
  • Move the cursor next to the desired screen number on a menu, type S, and press Enter.
  • Transfer directly to any product screen by typing an equal sign (=) followed by the complete screen number — for instance =5.2.2 — then pressing Enter.
  • Use PF keys to transfer to commonly used screens. The PF keys and defaults for the corresponding screens are as follows:

PF6

LOCATE * (2.L or 2.20)

PF13

Primary Menu

PF14

Memory Display screen (2.2)

PF16

Defined Storage screen (2.3)

PF17

Program Trace screen (2.4)

PF21

File Utility Menu (5).

Primary Menu (XPED/XPRT)

  -----------BMC AMI DevX Code Debug for CICS 17.02.00 PRIMARY MENU --------024
  COMMAND ===>
 PROGRAM:            MODULE:


   0  SESSION PROFILE      - Set default session attributes
   1  SESSION CONTROL      - Analyze summary of session events
   2  DEBUGGING FACILITIES - Interactively debug application programs
   5  FILE UTILITY         - Access datasets, temp stg, trans data, DLI, DB2
   7  ABEND-AID FOR CICS   - Interface to Abend-AID for CICS

   C  CODE COVERAGE        - Interface to Code Coverage
   G  XCHANGE/CICS         - Interface to Xchange's CICS Facilities
   P  CICSPLEX FACILITIES  - Access CICSPlex Control Facilities
   X  EXIT                 - Exit

      To set breakpoints in your program or keep specific data fields,
      enter your program name and use either the SOURCE command or PF key.

      For Online Technical Support refer to: www.bmc.com/support


      NOTICE:  Press PF2/PF14 to display the Copyright/Trade Secret Notice


While the Primary Menu is displayed, pressing PF2 or PF14 will display the copyright and trade secret notices as displayed in the following figure

Copyright/Trade Secret Notice Screen

---------------------------------- HELP FACILITY -----------------------------C024
COMMAND ===>                                                   SCROLL ===> CSR
MODULE:          CSECT:          **Hit PF1 again for help on using tutorials**
                                                          Help Module: DBUHLEGL
Commands: END (Prev screen)  CANCEL (Exit help)  UP  DOWN   Line     1 of    19  

(c)Copyright 1984 - 2020 Compuware Corporation.  All rights reserved.
(c)Copyright 1984 - 2023 BMC Software, Inc.   

 ----------------------------------------------------------------------------
|                          U. S. GOVERNMENT RIGHTS                           |
|  Use, duplication, or disclosure by the U.S. Government is subject to      |
|  restrictions as set forth in BMC Software, Inc license agreement          |
|  and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995),          |
|  DFARS 252.227-7013(c)(1)(ii)(OCT 1988), Far 12.212(a) (1995), FAR         |
|  52.227-19, or FAR 52.227-14 (ALT III), as applicable.                     |
|                           BMC Software, Inc                                |
 ----------------------------------------------------------------------------

THIS PRODUCT CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF BMC
SOFTWARE, INC.  USE, DISCLOSURE, OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR
EXPRESS WRITTEN PERMISSION OF BMC Software, Inc.  ACCESS IS LIMITED TO
AUTHORIZED USERS.  USE OF THIS PRODUCT IS SUBJECT TO THE TERMS AND CONDITIONS
OF THE USER'S LICENSE AGREEMENT WITH BMC Software, Inc.

XPSP Transaction

The XPSP transaction gives the CICS system programmer all the functionality of the XPED and XPRT transactions, and adds special CICS region-related utilities. When you access Code Debug CICS with XPSP, the Primary Menu displayed is similar to the XPED/XPRT Primary Menu, but with one additional option:

9 SYSTEM FACILITIES - Access global region analysis facilities

When you select option 9, System Facilities, you have access to the extended XPSP functions, which include:

  • A CICS storage and table editor
  • Power to activate storage protection anywhere in the CICS region
  • Ability to analyze hung (system suspended) CICS transactions and chain through CICS storage areas.

The System Facilities Menu  shows the additional functions available to the XPSP user.

System Facilities Menu (9) for XPSP Users

 ------------------------------SYSTEM FACILITIES MENU -------------------C024
COMMAND ===>
MODULE:          CSECT:


   1  VIEW SINGLE TASK    - View a selected task
   2  MEMORY              - Display/modify memory
   3  TASK LIST           - List all Tasks in the CICS region
   4  MONITOR FACILITIES  - Display/modify monitoring rules
   5  CSECT EXCLUSIONS    - Display/modify CSECT exclusions
   6  TRAP SUMMARY        - Display/modify global ABEND traps
   7  STORAGE EXCEPTIONS  - Display/modify global storage protection exceptions
   8  STORAGE PROTECTION  - Display/modify global storage protection entries
   9  SYSTEM LABELS       - Create system labels for storage areas
   D  DSECTS              - Display formatted DSECTs
   L  SLS DATASETS        - Process SLS datasets
   P  RESOURCE SUMMARY    - Display/remove global breakpoints/keeps

 

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