Emergency situations

In the event of an emergency procedure, several tasks must be performed as a prelude to complete shutdown of the entire system.

• All users must log out and leave the office: The AllUsersLogOut job runs a program that instructs all employees to do this immediately.

  NOTE: The purpose of the AllUsersLogOut job is to notify all users to log out and go home. It does this by shouting a very urgent notification message to this effect to all users. This shout action is defined in the job’s Actions tab in the Notifications after job completion area.

• All data centers must be informed that this data center can no longer function: The SetUpEmergencyGlobalCondition job performs this task by running a program that sends out a global condition to this effect.
• An emergency backup of all systems must be performed: This is performed by the BackupAllSystems job in the Ex-Backup Sub Application.

Only after these tasks are completed can systems be stopped. The jobs that stop the systems belong to a different Sub Application.

To simplify defining dependencies for these predecessor and successor jobs, and to simplify dependency definition changes that might be needed in the future (such as adding an additional predecessor job), an intermediate job, ShutDownAllSystems, is defined in the Ex-EmergencyProcs Sub Application. ShutDownAllSystems is defined as the successor job to the above jobs, and the predecessor job to the jobs in the Ex-ComponentStopping Sub Application that shuts down Control-M/EM components.

Defining jobs to initiate user logout and notify other data centers that this data center has an emergency shutdown

The AllUsersLogOut and SetUpEmergencyGlobalCondition batch jobs are not scheduled to run; they are irregular, emergency jobs. To execute, these jobs must be manually forced. If misused, these jobs can be exceedingly damaging to the company. Therefore, only the CEO or someone with similar permissions can actually force these jobs. And to ensure that the CEO does not erroneously do so, these jobs require confirmation before submission.

Once submitted, these jobs are more critical than any other jobs. They are therefore defined as critical jobs having the highest priority.

Defining the job type and other general information about the jobs

• In the General tab:
  • The File Name and Path fields identify the file name and location of the batch job.
  • In the Priority area: Due to the critical and urgent nature of these jobs, these jobs are defined critical, and assigns them the highest priority (99).
  • In the Created field: Due to the potential for harm from these jobs if inappropriately run, the Created by field identifies the person who can automate these following jobs by having the New Day Procedure run them:
    • AllUsersLogOut job: The CEO
    • SetUpEmergencyGlobalCondition job: The CIO
• In the Scheduling tab: These jobs are not scheduled. Rather, they are manually forced if needed. Therefore, they have no parameters defined in the Scheduling tab.
• In the Prerequisites tab: Due to the potential for harm from these jobs if inappropriately run, they require manual confirmation before they can execute. Manual confirmation is defined by selecting the Wait for Confirmation check box.
• In the Actions tab: An Out Condition is defined for each job (either condition can be used by the successor jobs) to establish the dependency between these jobs and their successor jobs. These jobs are predecessor jobs to at least one other job. The date defined for this Out Condition is Order Date, to ensure that the condition is added to the system with the working date the job was forced. An additional prerequisite condition is defined in the On Do Actions section as follows:
  • An On Specific statement output (statement= *** code=OK) is defined to instruct Control-M that the accompanying Do statement is performed if the job ends OK.
  • A Do statement adds a condition with a date value of Order date, indicating that the job’s task has been completed.

To initiate the shut down of all systems, see Initiating the shut down of all systems.