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.

message_backup

ntroduction

The purpose of this space is to provide a convenient cross-reference of the messages and ABEND codes issued by the following BMC products: Code Debug TSO, Code Debug IMS, and Code Debug Db2 Extension.

Besides system messages and ABEND codes, there are also other types of messages. Some are written to the source display during a test in a one line area after the command line, known as the message area. Others are simply written to the terminal in no specific format. These messages, however, are context sensitive and are intended to be self-explanatory. Unnumbered messages in the session log can also fall into this category.

Some processing errors are so severe that either the test or the compile must be shut down immediately. If Code Debug TSO itself abends, the appropriate action is always to contact your in-house technical support staff for Code Debug TSO, or Code Debug Db2 Extension. In some instances, your internal technical support contact can advise you to call the BMC Support.

Space Organization

The Code Debug Messages and Codes space is divided into five sections:

Intended Audience

Generally, recommended actions and explanations for Code Debug messages and abend codes are written for the installer and for the end user: the COBOL, Assembler, PL/I, or C Language programmer using one of the Code Debug products to debug their programs.

Accessing Other Products

Code Debug TSO and Code Debug IMS are fully integrated with 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 tools, such as Code Debug CICS and Code Debug CICS. From the Code Debug TSO Primary Menu, you can also access (if installed), File-AID/MVS and File-AID for IMS.

Notation Rules

The following notation rules apply:

  • Messages and abends are shown in the following format, when applicable:
    • Message number
    • Message
    • Module name, if required
    • Explanation of message
    • System action, if necessary
    • User action, if necessary.
  • Most messages are displayed in capital letters.
  • Messages appear in numerical order in the text.
  • Some messages are identified with a numeric negative value which precedes the message text. These messages correspond to Unsuccessful SQL (USQL) Error Codes.

  • Messages written to the session log and abend messages list one or more modules as the source of the message. This information is used by BMC Support to help answer your questions.

  • If the message or abend was generated in response to bad program data, the product can provide information as to the type of data (“X” for alphanumeric, “N” for binary or numeric) and data item length. Under certain circumstances, “C” could be either alphanumeric or a character. For example, “X(30)” means that up to thirty bytes of data (perhaps a data set name) will be inserted into the message.
  • Whenever a user abend occurs, there should be another message preceding it.

Enterprise PL/I for z/OS

The compiler for Enterprise PL/I for z/OS is somewhat different in the way it handles certain aspects of the language. One such difference involves the method by which statements are identified. Traditionally, each PL/I statement was given a unique statement number for identification in the various elements of the compiler output. Under Enterprise PL/I for z/OS compilation, however, the identification is less finite, with only the file and line number being used to discern between language constructs.

Because this mechanism is somewhat awkward when using Code Debug, the BMC Language Processor instead associates each file and line number combination with a single sequential line number. It is this generated line number which is used by Code Debug with Enterprise PL/I for z/OS programs as the replacement notation for statement number under previous PL/I compilers.

As a result, references to the term “statement” in Code Debug documentation, messages and panels actually see to the line construct (which may contain multiple statements) in an Enterprise PL/I for z/OS environment.

Documentation Availability

Online Documentation

The Code Debug TSO and Code Debug IMS product installation package does not include the product documentation. Access the Code Debug TSO documentation from the BMC Support Center in the following electronic formats:

  • Release Notes in HTML format
  • Product spaces in PDF format
  • Product spaces 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.

Information for Customer Solutions

If problems occur, consult your space or the Code Debug TSO technical support representative at your site. If problems persist, please obtain the following information before calling BMC Support. This information helps us to efficiently determine the cause of the problem.

For problems occurring during compile time, request Customer Solutions for BMC AMI Common Shared Services (CSS) and provide the following information:

  • Release level of compiler
  • List of other vendor products used
  • Abend module name
  • Any messages in CWPERRM ddname
  • Release of CSS.

For problems encountered before bringing up your program (front end problems):

  • Sequence of events leading up to the problem
  • Release and level of Code Debug product
  • Any ISPF error messages, operating system messages, and information provided in the TSO profile WTPMSG.

For run-time abends:

  • Release and level of Code Debug product
  • Any ISPF error messages, operating system messages, and information provided in the TSO profile WTPMSG
  • Information provided in the product session log data set at the time of the abend.

Important

When in-depth diagnosis is required, the following documentation will be requested from you:

  • Full SYSUDUMP (not Abend-AID dump) or SYSMDUMP
  • Source listing or tape of problem programs, including all copy books and members used
  • Listing of product session log at the time of the abend
  • Listing of the original compile.

If, as the in-house Code Debug technical support contact, you are unable to resolve an Code Debug product problem, the proper action is to call BMC Support directly.

 

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