Controlling message management
MPFLSTxx allows you to specify how you want to process WTO/WTOR messages. Message management refers to message suppression, message retention, message automation eligibility, and the use of installation-supplied WTO/WTOR exit routines.
Message suppression means that the message is logged in the hardcopy log, but it does not appear at an MVS™ operator's console.
Message retention means that action messages are saved by the action message retention facility (AMRF) on the action message retention queue. Retention allows the operator to view the message later. If you choose not to retain a message, the system will not add it to the action message retention queue.
- Modify the text of a message.
- Reroute a message to a different operator's console or to a different system for processing.
- Record some information that is contained in the message text for future use.
- Respond to the message.
An automation subsystem can look at the message text and the message attributes and perform the programmed action. You can use MPFLSTxx to identify whether you want a message to be eligible for automation processing. The automation subsystem must then select and process the messages. You can also use MPFLSTxx to indicate information to pass to an automation subsystem. Messages that are eligible for automation processing can also be suppressed or retained. Message suppression and retention are functions separate from automation. The Tivoli NetView for z/OS subsystem recognizes the message automation eligibility specifications in MPFLSTxx.
Your installation might have installation-written exit routines to handle WTO/WTOR messages. Through MPFLSTxx, you can specify which messages are to go to which exit routine. The exit routine can examine the message text and the message attributes and decide whether to suppress, retain, or take other actions on the message. The exit routine can also examine and modify the token.