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 TSO with an Assembler program

Introduction

This space introduces you to Code Debug TSO and Code Debug IMS, using a series of examples that demonstrate simple and advanced debugging techniques that can be applied to your application development and maintenance needs. It describes how to use Code Debug TSO facilities in the Assembler context with minor references to mixed language debugging support. Additional information is provided in other spaces; see to Related Publications.

Related topics

Product-features

Organization of sections

This space contains the following topics:

Code Debug TSO Overview: Summarizes the functions and features of Code Debug TSO and Code Debug IMS.

User Interface to Code Debug TSO: Describes the Source screen format, default PF keys, command processing, and attention key processing.

Quick Sample Debugging Session: Provides a short tutorial highlighting the basic debugging features of Code Debug TSO.

Getting Started: Describes the online Compile Facility, which is used to prepare your programs for debugging with Code Debug TSO. Also describes how to start a Code Debug TSO debugging session in interactive mode, in batch mode using the Batch Connect facility or the Multi-Batch Facility, and how to manually change your execution JCL to start a batch session.

Debugging Interactively: Describes how to use Code Debug TSO commands to control execution, inspect data, analyze logic, modify logic, debug sourceless programs, and other debugging functions.

Handling Run-Time Errors: Describes how to analyze and apply fixes for abends.

Debugging With Code Debug IMS: Describes how to start a Code Debug IMS debugging session.

Debugging With Db2 Stored Procedures: Provides general information about debugging Db2 stored procedures.

Debugging Programs With Special Conditions: Provides general information about debugging certain types of programs.

Using the File Allocation Utility: Describes how to access and use the File Allocation Utility.

Code Debug TSO Environment Test Screens: Provides full descriptions of all environment test screens.

Specifying Setup Options: Describes how to specify and override the installed setup options such as the load library, DDIO file, Db2 system name, and so on.

Specifying Session Defaults: Describes how to specify terminal characteristics, PF key definitions, screen colors, user profiles, and so on.

Code Debug TSO Utilities: Describes the Code Debug TSO utilities that let you create and maintain source listings, display available memory, display file allocations, and convert and merge user profiles.

Binding the Application Plan or Package: Describes how to bind Db2 programs.

DBCS Support: Describes the double-byte character set support.

Debugging a Client Application and Db2 Stored Procedure: Describes how to debug a Db2 stored procedure along with the client application that calls it.

Intended audience

This space is intended for use by Assembler programmers. A working knowledge of Assembler and your local operating systems is assumed.

Accessing other products

Code Debug TSO and Code Debug IMSare fully integrated with BMC’s File-AID for DB2 and Abend-AID. From the Code Debug TSO Primary Menu, you can access a CICS region where you can use other BMC tools, such as Code Debug CICS and Abend-AID for CICS. From the Code Debug TSO Primary Menu, you can also access (if installed), File-AID/MVS and File-AID for IMS.

Notation rules

This space uses the following notation rules:

  • Uppercase characters are used in text for commands, keywords, and function keys.
  • Screen titles appear in text with initial capitals.
  • Screen fields, prompts, and messages are capitalized as displayed.
  • Information that the user enters is shown in bold type.
  • Occasional data set and library member names are shown in bold type for emphasis.
  • Commands are not considered case sensitive; they can be typed in all lowercase in the command area.

 

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