gtpm4m05Messages (System Error and Offline)

Offline Message Formats

When you see an offline message on your screen or read it in a dump, you will notice that the message has one of the following formats.

Format
Description

ppppnnnnx hh.mm.ss text
Message with the standard message ID.

text
Message without the standard message ID and with text only.

xx,yy text
Message without the standard message ID that begins with variable text.

*xppp* text
Offline ACF/SNA table generation (OSTG) program error messages without the standard message ID.

aaanum text
System generation messages without the standard message ID.

Standard Messages

Messages with the standard message ID have the following format.

ppppnnnnx hh.mm.ss text

When reading from left to right, this format contains the following parts.

Part
Description

ppppnnnnx
The standard message ID has the following parts:

pppp
Represents the first 4 characters of the segment name or the secondary action code of the associated input message.

nnnn
Represents a unique message number.

x
Represents one of the following severity codes:

I
Information only, which indicates the message is a normal response.

A
Action required, which indicates that additional operator action is required.

W
Attention, which indicates an error that could require additional user action.

E
Error, which indicates an error without program shutdown.

T
Termination, which indicates an error with program shutdown.

hh.mm.ss
Time stamp represents the time that the message was built. When you search for a message, ignore the time stamp because it is not shown in this information.

text
The text of the message.

Non-Standard Messages

Messages without the standard message ID are shown with the following formats.

Locate an Offline Message

There are two ways to locate an offline message depending on whether the message does or does not have the standard message ID.

If a message has the standard message ID, the message IDs are listed in increasing numeric order preceded by their alphabetic prefix. To find a message with the standard message ID, record the message ID from the message (for example, IPTS0004E) and then use the message ID to search for the message.

If a message does not have the standard message ID, the message is listed in one of the following ways:

Analyze an Offline Message

Once you locate the message, you will notice that the message ID and the message text are framed in a box for quick access. In the message text, variable information is shown in italicized lowercase letters. When a message actually occurs, specific information is provided for the variable information in the message that is displayed on your screen or printed in the dump. Explanations of the variable information are described immediately following the message text or in the actual explanation of the message.

Below each message you will find some or all of the following pieces of information to help you analyze the message.

Standard Message Example

The following is an example of how an offline message with a standard message ID and its associated information is presented.

IPTS0004EINVALID PARAMETER: parameter

Where:

parameter
The specified parameter.

Explanation: The value specified for the PARM parameter in the job control language (JCL) for the IPTPRT utility is not a valid input parameter.

System Action: The postprocessor request is rejected.

User Response: Do the following:

  1. Update the EXEC statement in the JCL for the IPTPRT utility, and specify a valid parameter for the PARM parameter.
  2. Run the JCL again.

See TPF Transmission Control Protocol/Internet Protocol for more information about the IPTPRT utility.

Non-Standard Message Examples

The following is an example of how an offline message with text only and its associated information is presented.

000000000DATA GENERATION -- BAD DELIMITER -- REST OF CD IGNORED

Explanation: The proper delimiter for this field of four decimal digits was not found.

System Action: The remainder of this card is ignored.

User Response: None.

See TPF Program Development Support Reference for more information.

The following is an example of how an OSTG error message and its associated information is presented.

*S001* OSTG CANCELLED DUE TO PARM ERROR The PARM parameter of the EXEC statement was not specified correctly. See the messages on the OSTG report for the specific error.

System Action: The table generation process is ended.

User Response: Do the following:

  1. See the messages on the OSTG report to determine the cause of the error.
  2. Correct the PARM parameter.
  3. Run the OSTG job again.

See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.

The following is an example of a system generation message.

MSA001TOO MANY APPLICATIONS SPECIFIED FOR MESSAGE ROUTER

Severity: 5

Explanation: The message router macros support only up to 256 application programs.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP Stage I.

See TPF ACF/SNA Network Generation for more information about the offline ACF/SNA table generation (OSTG) program.