Normal operator actions (DBCTL)

The DBCTL MTO can control the DBCTL environment from any z/OS® system console. If your MTO operates from a different console (secondary system console) from the primary one where the z/OS operator sits, you must ensure a means of communication between the two operators.

DBCTL requests for tape or DASD mounts must be given to the system console operator. Some IMS messages (DFS prefix) originate from the CCTL region and thus appear on the primary system console; these messages should be relayed to the MTO in case some action needs to be taken. For example, when the CCTL tries to connect to a DBCTL environment and the DBCTL subsystem is not yet running, the IMS database resource adapter (DRA), which is part of the CCTL region, issues message DFS690A. In general, communication between the CCTL operator and the MTO is important.

As in the DB/DC or DCCTL environments, the z/OS operator can start IMS BMPs by using either the IMSRDR or the IMSBATCH procedure. Any activity of IMS dependent regions or utilities the z/OS operator controls should be recorded or communicated so that the MTO is aware of all IMS-related activity.

The following table shows the actions usually performed by the MTO and the commands usually reserved for the IMS DBCTL master terminal.

Table 1. Master terminal operator actions usually performed
Activity IMS command
Activate IMS (cold start) /ERESTART COLDSYS
Start a BMP /START REGION IMSBMP
Display dependent regions /DISPLAY ACTIVE
Shut down IMS /CHECKPOINT FREEZE
Restart IMS (warm start) /NRESTART