Product architecture of Code Debug CICS COBOL

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, COBOL, C, or PL/I, plus a variety of other programming languages on an 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, by default 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), Task Storage Display (2.S), 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 the section entitled Restricted Operating Modes in the Code Debug CICS Reference Manual.

This section also provides infromation about the following topics: