Specifying message management

For the messages that you specify in MPFLSTxx, you can indicate that the system is to:
  • Suppress specific messages or all messages that begin with a particular prefix. SUP(YES/NO) provides this option.
  • Retain action messages (descriptor codes 1, 2, 3, 11) using the action message retention facility (AMRF). The RETAIN parameter allows you to selectively retain certain types of action messages (immediate, eventual, or critical eventual).
  • Allow an automation subsystem, such as NetView®, to respond to the WTO/WTOR message(s) that you specify. AUTO(YES/NO/token) allows you to identify whether a message is eligible for automation processing and to pass information (a token) to the automation subsystem.
  • Pass control to an installation-supplied WTO/WTOR exit routine to process the message(s). The USEREXIT option allows you to identify the exit routine.
  • Assign installation-supplied defaults for specific messages that are identified in the MPFLSTxx member. The .DEFAULT statement allows you to change the system-assigned message processing defaults for any message you specify.
  • Assign installation-supplied defaults for messages that are not identified in the MPFLSTxx member. The .NO_ENTRY statement allows you to indicate how the system is to handle messages that are not specified in the MPFLSTxx member.
  • Indicate or flag the beginning of particular messages that are written to the JES3 hard-copy log. The MPFHCF statement allows you to specify the character you want to use as an indicator.
Parent topic: Controlling message management