System Shutdown

This solution contains sample rules for automated shutdown using Control-O. The shutdown process is initiated by issuing operator command SHUTSYS from the master console. The operator is then requested to issue command SHUTSYS again for confirmation. System shutdown actually starts only if command SHUTSYS is issued twice during one minute.

When shutdown is started, active system components (started tasks, initiators, lines, and so on.) are stopped. Checks are performed cyclically to determine the status of the various system components. If all systems are down, Control-O is restarted with SUB=MSTR (that is, under MVS rather than under JES2) and JES2 is stopped. Control-O brings itself down when JES2 termination is completed.

SHUTSYS rules are designed to provide the level of flexibility and modularity required for meeting the various shutdown requirements of different sites. Different system components (such as Control-M and CICS) are stopped and monitored by different rules. These rules all have a similar logic and structure, and with minimal adaptation they can be easily duplicated to handle other system components.

Dependencies among SHUTSYS rules are indicated in the diagram on the following page.

Note: All prerequisite conditions defined in this solution must be initialized (deleted) at time of IPL. This is especially important for SHUTSYS rules, because the unintended addition of prerequisite conditions may initiate the undesired shutdown of system components. For more details, see SolveWare Initialization.