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.

Using Code Debug CICS with COBOL program

This section provides step-by-step instructions on how to use Code Debug CICS to solve common debugging problems. To become acquainted with Code Debug CICS, you should first review Product Overview and Getting started.

The following sections listed contain exercises using common examples. The first examples show how to access and exit the product and how to debug a simple transaction. Subsequent topics provide exercises on how to set breakpoints in a program, how to step through the program, and how to change storage. The later topics provide exercises on advanced features.

The exercises cover only a portion of the many Code Debug CICS screens and functions. For more information on these topics, see the Code Debug CICS Reference Manual.

This space contains the following topics:

Product Overview: Introduces Code Debug’s facilities and discusses the need for an interactive debugging tool. The overview also includes features that are new to this release of the product.

Getting started: Shows how to prepare your application for debugging, accessing, and exiting Code Debug CICS.

Testing a COBOL program: Shows how to test an application transaction with and without breakpoints, and how to inspect program data.

Debugging Applications Without Source Code: Provides tips on performing sourceless debugging.

Debugging Subroutines: Provides tips on setting breakpoints in the calling and called programs and selecting and excluding CSECTs.

Analyzing Program Execution: Describes how to set up program analysis.

Monitoring Tasks Started from Remote Terminals: Describes how to set and intercept remote traps.

Providing Storage Protection: Shows how to handle storage violations and set region-wide storage protection.

Interfacing with Abend-AID for CICS: Discusses the interface with BMC’s Abend-AID for CICS fault diagnosis product.

Using Automatic Trap Activation: Explain how ATA traps abends without the user having a Code Debug session active.

Setting Up a Profile: Describes how to set up a customized environment that modifies program default values.

Accessing Files: Shows you how to browse records, change file service requests, and work with data and storage queues.

Accessing DL/1 Databases: Shows how to list PCBs and edit a DL/I segment.

Using Code Debug CICS with Db2: Tips on row and column editing of Db2 tables and views.

Using Code Debug CICS with MQ: Describes the MQ File Utility and how to debug MQ programs.

Accessing CICS Storage: Describes how to access and update CICS storage.

Using Global Storage Protection: Shows how to set protection, define system labels, and control storage exceptions.

Editing CICS Tables and Control Blocks: Describes how to display CICS table entries and DSECTs.

Using 3270 Web Bridge Support: Demonstrates how to run Code Debug using the 3270 Web Bridge function.

Glossary: Describes Code Debug CICS features and defines key terms.

Intended audience

Code Debug CICS is structured in three levels to accommodate several types of users. The audience for this manual may differ, depending on the experience of the user and the transactions for which the user is authorized. The following three transactions are used to describe Code Debug’s three levels:

  • XPED – Intended for application programmers who want a source level focus.
  • XPRT – Intended for application programmers who want a break/abend focus.
  • XPSP – Intended for experienced system programmers who are authorized to update CICS tables and control areas.

System environment

For the most current system environment information, see the Code Debug CICS Installation and Configuration Guide.

Information for customer solutions

If problems arise, please check your manual for assistance. If problems persist, please obtain the following information before calling BMC Support for assistance. This information will help determine the exact cause of the problem as quickly as possible.

  1. Identify the release number of BMC products in use.
  2. Identify the operating system.
  3. Identify the release of CICS Transaction Server that is being used.
  4. If an abend occurs, note the displacement and the module in which it occurs. If possible, obtain a copy of the system dump.
  5. Note the sequence of steps (including all commands issued) that resulted in the problem. Also note any variable data types and programming languages involved.
  6. To receive product fixes electronically, be ready to provide your email address.

Online documentation

The Code Debug CICS product installation package does not include the product documentation. Access the Code Debug CICS documentation from the BMC Supportin the following electronic formats:

  • Release Notes in HTML format
  • Product manuals in PDF format
  • Product manuals in HTML format.

The product documentation is available for viewing or downloading:

  • View PDF files with the free Adobe Reader.
  • View HTML files with any standard web browser.

This section provides information about the following topics:

 

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