RUN-TIME MESSAGES - IBM Mainframe

If the operating system detects a serious problem in your program, it may halt execution of your program. An example of this situation is an addressing exception-where your program is trying to access a part of main storage beyond its own bounds. The premature termination (known as an abend) is indicated by a message from the system. The format of the run-time messages produced by the VS COBOL II subroutine library is:

ICZnnnl-text of message.

The message number, nnn, also corresponds to the last three digits of a user abend code which has the format Ulnnn. User abend codes in the range of 1000 through 1999 are used by VS COBOL 11. So, you should avoid using these if you plan to write your own user abend routines.

In a CICS environment, the message number, nnn, also corresponds to the last three digits of a CICS transaction abend code that has the format Innn. Transaction abend codes in the range of 1000 to 1999 are used by VS COBOL II and thus should not be used.

You can identify the origin of these messages by their prefixes. For example a prefix ICE means it is a message from the Sort program, a prefix of IGZ means it is a message from the VS COBOL II subroutine library, etc.

The text of the message will explain the error, and usually you can use that information to fix the problem. In a non-CICS environment, run-time messages are written using OS write-to-programmer; in CICS, they are written to the temporary storage queue, CEBRxxxx, where xxxx is the terminal-id associated with the transaction.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Mainframe Topics