Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Defining message levels for a console z/OS MVS Planning: Operations SA23-1390-00 |
|
Assigning routing codes is one way to limit message traffic to a console. You can further reduce the number of messages that appear on a console by directing certain messages to consoles by message levels. Descriptor codes can also appear with messages and further describe the significance of the message levels. The system differentiates among the following kinds of message
levels:
Descriptor codes and message levels The system gives special consideration to messages with descriptor codes 1, 2, 3, 11, 12, and WTOR messages. MVS also handles messages with descriptor code 13 in a special way. If a message has been specified for automation in MPF, you can assign descriptor code 13 to the message in a message processing exit (like IEAVMXIT) to indicate that the message has been previously automated. You can then reissue the message. Descriptor code 13 can be useful when a message has been automated on one system in a sysplex but needs to be reissued to other systems in the sysplex. To define message levels for a console, use the following keyword
on the CONSOLE statement:
Assignment by message level means that a console can accept combinations
of action, broadcast, and informational messages that the system sends
to a console. Options you can specify for LEVEL include the following:
You can specify one or any combination of these options for LEVEL. If LEVEL in the CONSOLxx member is not coded, the system sends all messages, including broadcast messages, to the console. To direct only WTOR messages and immediate action messages to a
console named ACCT, code this statement in CONSOLxx:
Operators can use the CONTROL V command to change LEVEL. |
Copyright IBM Corporation 1990, 2014
|