bdfm1m06 | Messages (System Error, Online, Offline) and Master Glossary |
Online messages and offline messages result from less severe conditions than system error messages, can originate from online or offline processes, and are not normally accompanied by dumps. Like system error messages, online messages are issued by the TPFDF product when running in a TPF system or in an ALCS environment, while offline messages occur in programs under IBM MVS control. The severity of the error determines whether a message is a system error message or an online message. Online messages are usually those issued by a TPFDF utility, such as TPFDF data collection (ZUDFC).
When you see an online or offline message on your screen or read it in a dump, you will notice that the message has one of the following formats:
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:
Messages without the standard message ID are shown with the following format:
ttttttttt text
When reading from left to right, this format contains the following parts:
In the top outer corner of each page you will find the range of message IDs listed on that page (for example, UDFC0016E * UDFC0019E). This means that the first online or offline message on the page is UDFC0016E and the last online or offline message on the page is UDFC0019E.
There are two ways to locate an online or 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, UDFC0061E. Then, use the first 4 characters of the message ID to locate the section where these messages are listed. Finally, use the remaining numbers and characters that make up the message ID to find the message. In this example, the first 4 characters are UDFC while the remaining numbers and characters are 0061E.
If a message does not have the standard message ID, the message is listed with a message ID of 000000000 and then presented in alphabetic order based on the initial message text.
To find a message without the standard message ID, record the message text from the message; for example, UNABLE TO PROCESS - LOG FILE CORRUPTED. Then, locate the section where the messages with a message ID of 000000000 are listed. Finally, use the message text to find the message.
Once you locate a 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 the following information to help you analyze the message.
Notes:
The following provides examples of online and offline messages with and without standard message IDs.
The following is an example of how an online or offline message
with a standard message ID and its associated information is
presented.
UDFC0061E | PROGC ERROR RETRIEVING UF0A/UFA2 PAT ADDRESS |
Explanation: Data collection cannot be started because an error occurred while retrieving the program allocation table (PAT) address of UF0A or UFA2. Without this address, data collection cannot determine if these programs are in an active loadset.
System Action: Data collection is not started.
User Response: Do the following:
See TPFDF Utilities for more information about the
ZUDFC START command.
The following is an example of how an online or offline message
without a standard message ID and its associated information is
presented.
000000000 | ZFCRU- operation IMPOSSIBLE TO EXECUTE - NO POOL AVAILABLE |
Where:
Explanation: An error occurred when you entered a ZFRCRU command because no pool records are available.
System Action: The ZFCRU command is rejected.
User Response: Do the following:
See TPFDF Utilities for more information about the
ZFCRU commands.