How to use AOI to complete different tasks

Discarding unwanted messages

You can write an AO exit routine to prevent the master terminal (z/OS® system console in the DBCTL environment) from being flooded with unwanted IMS messages. You can still log discarded messages to the secondary master terminal (by issuing the /SMCOPY command from an AO application program) in case, for example, the messages are subsequently needed for problem determination.

You can also prevent the logging of IMS system messages to the secondary master terminal by using the /SMCOPY MSG OFF command.

Messages that are logged to the secondary master can also be controlled using a type-2 AO exit routine (DFSAOE00 or another AOIE type exit routine).

Setting up a batch window

You can write an AO application to set aside time (usually each night) for running batch jobs, that is, to set up a batch window. When you run batch jobs, you usually take the databases offline. To set up your batch window using an AO application program, you can write a multiple step job that:

• Issues a /DBRECOVERY DB or UPDATE DB STOP(ACCESS) command to take the database offline (BMP step)
• Issues a /DISPLAY DB or QUERY DB command to determine when the database is actually offline (BMP step)
• Initiates your batch work and does routine operational tasks, such as making image copies (batch step)
• Issues a /START DB or UPDATE DB START(ACCESS) SET(ACCTYPE()) command to bring the databases online (BMP step)

Restarting application programs after an abend

When an application program abends, IMS issues a message and immediately stops the program. You can write an AO exit routine that sends the message to an AO application program that can then issue the /START PROGRAM command to allow work to continue immediately, rather than waiting for the MTO to restart the program.

Customizing messages

You can write an exit routine that customizes IMS system messages before they are routed to the master terminal. You can delete parts of messages that have no meaning for the MTO. You can reformat a message to conform to a format established at your installation. Or, you can add text to a message to tell an MTO what action to take in response to the message.

Creating an audit trail

You can use AOI to track system or user actions. For example, if you find that certain commands are not being used appropriately at your installation, you can intercept them with an AO exit routine. The AO exit routine can send a copy of the command to an AO application, which can in turn send the command, with pertinent user information, to the MTO, or copy it to the log for later analysis.

Supervising terminals

If your network is extensive, you might make one or more terminal operators responsible for terminal availability. These operators also watch for communication problems and can reassign LTERMs to alternate devices. You can write an AO application program that performs the same tasks, and in effect, functions as a supervisory terminal. Either the MTO or someone entering the appropriate transaction from a remote terminal can schedule the AO application program.