Secondary master terminal and auditing operational control

Some IMS commands are automatically copied to the terminal designated as SECONDARY in the system definition NAME macro. If you specify COPYLOG=ALL in the COMM macro during system definition, then when other terminals besides the master terminal enter any of these commands, copies of an entered command and its response are sent to the secondary master terminal.

To understand the actions taken by the MTO, you should obtain a permanent printed copy of the command sequences issued by the MTO. This function is termed hardcopy logging.

The MTO can use the /SMCOPY MASTER OFF command to override the logging of commands to the secondary master terminal. The MTO can also use this command to turn off logging of command entry and responses from other terminals. To resume logging to the secondary master terminal, the MTO can use the /SMCOPY MASTER ON [TERMINAL ON] command.

This more permanent record is valuable for several reason, but the principal one is that of accountability. You can also use the output to audit whether the operations command sequence and timing are providing committed service. The checklist in the following table identifies the types of activities and related commands, and shows some of the ways you can use the secondary master terminal output.

Table 1. Using secondary master terminal output to audit performance
Type of activity	Command	Output usage
Network control	/OPNDST	Check VTAM® connection procedure.
	/CLSDST	Check VTAM disconnect procedure.
	/RCLSDST	Check expected disconnect.
	/START	Check network availability.
	/RSTART	Coordinate with terminal usage.
	/STOP	Investigate stopped resource.
	/IDLE	Investigate if there is lost or waiting output.
	/MSASSIGN	Check if planned MSC connect.
Device control	/COMPT	Check planned VTAM component switch.
Device control	/RCOMPT	Check remote VTAM component allowed.
Resource control	/ASSIGN	Check that all uses fit operations plan.
	/START	Check region availability and queue control.
	/STOP	Investigate all events.
	/PSTOP	Investigate why input stopped.
	/PURGE	Investigate why service was restricted.
	/MODIFY	Audit the extent and timing of online changes.
	/CHANGE	Check size of MFS dynamic directory.
Security	/MODIFY	Set timing of authorization and password changes.
Recovery	/DBRECOVERY	Investigate database errors.
	/DBDUMP	Investigate database errors and subsequent processing.
	/DEQUEUE	Investigate lost message or output.
	/CHECKPOINT	Coordinate with reported errors.
	/SWITCH	Investigate reasons for unplanned takeover activity.
	/UNLOCK SYSTEM	Investigate takeover activity.
Monitoring	/DISPLAY	Incorporate in monitoring feedback. Check use for scheduling.
Monitoring	/TRACE	Coordinate with trace output.
HALDB OLR	/INITIATE	Initiate or resume HALDB Online Reorganization (OLR).
	/TERMINATE	Stop HALDB OLR.
	/UPDATE	Change the rate or the disposition flag of the DEL or NODEL data set of a HALDB OLR, or the disposition flag of REL or NOREL to release ownership of OLR at normal or abnormal shutdown of IMS.