Record-keeping procedures for the MTO

The master terminal operator (MTO) needs to keep various types of information that document system activity. Consider designing standard forms or online panels for recording this information.

The MTO needs to record the following general types of information:

Some of this information can be recorded automatically. DBRC records all OLDS and archive activity, and can also record the execution of batch jobs and recovery-related utilities.

By default, the master secondary terminal provides a hardcopy log of IMS system activity, including checkpoint information and IMS messages. The logging of IMS system messages to the secondary master terminal can be disabled by using the /SMCOPY MSG OFF command.

You can also have the secondary master terminal provide a hardcopy logging option for certain IMS commands and command responses by specifying the COPYLOG keyword in the COMM system definition macro or by issuing the /SMCOPY command with the appropriate keyword.

The information logged to the secondary master terminal can be helpful when tracking a series of events affecting the operation of IMS, or when verifying that an operations task was performed. Information useful for analyzing an IMS error situation is often in the z/OS® hardcopy log.

You can select whether IMS logs commands issued from the master terminal or commands entered from other terminals, or both. In either case, IMS only logs certain commands. When you issue a command from a terminal other than the master terminal, IMS logs output and identifies its node, or line and physical terminal number.

The /SMCOPY command starts and stops the hardcopy logging facility for commands, system messages, or both.

IMS logs the following commands to the secondary master terminal: