Abstract for MVS System Messages
Purpose of this information
- Operator messages that are issued by the BCP and DFSMS.
- Log messages that are issued by the BCP and DFSMS.
- Some SYSOUT messages that are issued by the BCP and DFSMS. SYSOUT messages are issued by utilities that normally run in batch, such as SPZAP.
- Batch job messages that are issued by the BCP. Messages that are issued by JES2 or JES3 for batch jobs are in the JES messages information.
Usually, messages that are issued at interactive terminals (like TSO/E and CICS® terminals) are documented by the specific elements and products that support those terminals.
This information also contains the routing and descriptor codes that IBM® assigns to the messages that z/OS® components, subsystems, and products issue. Routing and descriptor codes are specified by the ROUTCDE and DESC keyword parameters on WTO and WTOR macros, which are the primary methods that programs use to issue messages. The routing code identifies where a message is displayed. The descriptor code identifies the significance of the message and the color of the message on operator consoles with color.
For more information about messages, including the message format, prefix by component, and more,
see the Introduction
section in z/OS MVS System Messages, Vol 1 (ABA-AOM).
Who reads messages
- Initialize the operating system and its subsystems.
- Monitor system activity.
- Keep the system or systems correctly running.
- Diagnose and correct system problems.
- Diagnose and correct errors in problem programs.
Where to find the most current message information
MVS System Messages documents are cumulative. As messages are added to the system, they are added to the documents. Similarly, when messages are changed on the system, they are changed in the documents. However, when a message is deleted from the system (no longer issued), the message is not deleted from the document. You can always look in the most recent message documents for the most current descriptions of system messages.