Initiating the shut down of all systems

The ShutDownAllSystems batch job runs a program (through the setting of an Out Condition) that enables another set of jobs to shut down Control-M/EM components. ShutDownAllSystems can only run after its predecessor jobs have ended successfully.

Defining the job type and other general information about the job

• In the General tab:
  • The File Name and File Path fields identify the file name and location of the batch job.
  • The Created by field: Due to the potential for harm from this job if inappropriately run, the CIO is defined in the Created By field. Only the person named in the Created By field can automate this job by having the New Day Procedure run it.
  • Priority field: The job is treated with the highest priority because of the critical and urgent nature of this job.
• In the Scheduling tab: This jobs is not scheduled. Rather, it is manually forced if needed. Therefore, it has no parameters defined in the Scheduling tab.

Ensuring that this job does not run until its predecessor jobs have ended

ShutDownAllSystems initiates system shut down. It must not run until:

• All users have logged out (initiated by the AllUsersLogOut job)
• All system files have been backed up (initiated by the BackUpAllSystems job)
• All other data centers have been notified of the shut down (initiated by the SetUpEmergencyGlobalCondition job)

To ensure that it runs only after all its (above-mentioned) predecessor jobs have ended successfully, ShutDownAllSystems contains the following definitions:

• In the Prerequisites tab, In Conditions match the conditions defined in Do Condition statements in the predecessor jobs. These In Conditions are assigned Order Date.
• In the In Conditions area there is an AND relationship between the In Conditions.

Ensuring that successor jobs can run

This job is a predecessor job to most of the shut down jobs in the Ex-ComponentStopping Sub Application. To enable the successor jobs to run, after ShutDownAllSystems adds the following Out Conditions (with an Order Date) after it ends successfully:

• ShutDownAllSystems-ENDED: This condition defines this jobs as a predecessor job for the remaining jobs in this folder (this Out Condition is defined as an In prerequisite condition for those jobs).
• EX_ShutDownAll: This condition serves as an indicator that this job ended for any other jobs that might need to know.

To handle component shutdown needs, see Handling component shutdown needs.