The Ex-ITMaintenance application - organizing the IT department maintenance jobs
Control-M comes with a number of examples that you can open in Control-M . To load this example into Control-M , see Job definitions examples.
The IT department runs a number of maintenance jobs of different types that are collectively organized into the Ex-ITMaintenance application. Most of the jobs in the sample draft, perform tasks that must be performed in extreme emergencies (fire, floods, tornado watch, etc). The draft also contains a job for routine, non-emergency backups.
During an extreme emergency, it is imperative that emergency procedures be immediately implemented to get employees to safety, get the system backed up, and to shut down Control-M components. The sequencing of these jobs is important, and this, in turn, affects the Sub Applications of these jobs.
Jobs in this application fall into the following Sub Applications:
Ex-Backups: Jobs to perform backup, in both non-emergency and emergency situations
Ex-EmergencyProcs: Jobs to initiate emergency procedures in an extreme emergency
Ex-ComponentStopping: Job to shut down Control-M components after the emergency procedures have been implemented
Handling IT job backup needs
The Ex-Backups Sub Application contains the following two jobs:
The Backups job performs a standard backup of company data under normal circumstances, which executes an operating system command (“copy”) to back up certain files from a directory to one of two tape drives. It should be scheduled every day (Scheduling tab - Every Day). Depending on the files being backed-up, this job copies the files to one of two tape drives. To ensure that these tape drives are available, in the Prerequisites tab, Quantitative Resources area indicates that two tape drives are required. The job is not submitted unless the drives are available and reserved for the job.
The BackupAllSystems job is executed only in extreme emergencies. It is not scheduled to run but is instead manually forced when needed. Because this critical batch job can be very damaging to the company if misused, only the CIO (Chief Information Officer) can force it. The job requires a large number of tape drives, has no predecessor jobs, and must complete the emergency backups before other jobs can shut down all systems. Once submitted, this job is the highest priority (Priority Very High). Note the following:
In the General tab, the File Name and Path fields identify the file name and location of the batch job. As this jobs is intended only for an extreme emergency, it is created by the Chief Information Officer (Created By field). As already noted, this job is not scheduled (None (Manual Order)). Rather, it is manually forced if needed.
BackUpAllSystems must back up all systems to tape. It requires 50 available tape drives before it run. These are defined as Quantitative Resources in the Prerequisites tab.
BackUpAllSystems is a predecessor job to at least one other job. To establish the dependency between this job and its successor jobs, the following prerequisite conditions are defined (either can be used by the successor jobs):
An appropriate Out Condition is defined in the Actions tab. The date defined for this Out Condition is the keyword, Order Date, to ensure that the condition is added to the system with the working date the job was forced.
An additional On Do Action is defined as follows:
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.
This condition could have alternatively been defined as an Out Condition.
After this job has ended successfully (that is, completed the backups), it shouts a very urgent notification to the CIO indicating that All Systems are backed up (Notifications after job completion area).
