Configuring message disposition

Edit online

You can use message disposition to suppress messages from the IMS master terminal (MTO), the IMS Administration Tool message log, or the IMS secondary master. You can also use message disposition to route messages to an automated operator interface (AOI) token.

Message disposition overview

IMS Administration Tool message disposition processing is controlled by user-defined tables that are stored in the options data set and that are loaded into storage at IMS start up. Multiple IMS systems can be defined to load the same tables from the options data set, but they do not share the tables after the tables loaded into memory.

You use the IMS Administration Tool user interface to add message IDs to the message tables and specify their disposition. The messages can be suppressed from the IMS master terminal or the IMS Administration Tool combined message log.

Message disposition tables can be updated without requiring an IMS startup.

Message disposition is invoked as part of the IMS automated operator interface (AOI) exit:
  • DFSAOE00, if you are implementing a non-refreshable user exit.
  • ATYAOE00, if you are implementing a refreshable user exit.

    DFSAOE00 is not used if you are implementing a refreshable exit routine.

You can also write your own AOI exit to suppress messages that would otherwise be sent to the IMS master terminal, or to route the messages to an alternate destination.

You can use message disposition to:
  • Suppress messages from the IMS master terminal.
  • Suppress messages from the IMS Administration Tool message log.
  • Suppress messages from the IMS secondary master terminal.
  • Route messages to an AOI token.
  • Manage message disposition tables and the list of messages designated for disposition.
  • Dynamically refresh the list of messages without an IMS restart.
  • Help control or eliminate messages from user-developed code.