Running CA WA CA 7 Edition for job scheduling facilitates restoring batch processing after a system down disaster. The nature of the outage and the level of preplanning is an important factor in determining disaster recovery procedures.
The initialization file has two statements, DRMODE and DRCLASS, which are used to define the options for Disaster Recovery and to activate DR Mode.
The DRCLASS statement can specify one or more disaster recovery classes that are active.
Business Value:
In CA WA CA 7 Edition, the Disaster Recovery Mode option permits the inclusion of only specified workloads in processing. Identifying the appropriate components for a given disaster is obviously one of the major challenges. The DRMODE option allows for a global default disaster class and the ability to define a specific job to a particular class. When running in Disaster Mode, the Schedule Scan function makes the appropriate determination of what work to submit based on the active disaster recovery classes.
Additional Considerations:
The following are Disaster Recovery Mode examples.
Example: Define a class to include jobs without DRMODEs
A default class can specify to include all jobs without a DRMODE defined. You can also use a special reserved word, @SYSTEM to use the job’s SYSTEM name as the disaster class.
DRCLASS,DEFCLASS=@SYSTEM
Example: Define default disaster recovery class DR1
This example states that the default disaster recovery class is DR1. This default applies to all jobs without a disaster class defined.
DRMODE,DEFCLASS=DR1
Some special considerations apply when running in Disaster Recovery Mode. Do you want to consider requirements for jobs during recovery? Do the requirements apply to triggers also? Should a job not in an active DR class that a job in an active DR class triggers run nonexecutable? Two keywords control the handling of requirements and triggers.
For requirements, set the RQMTS= keyword to DR or ALL. If the predecessor job's disaster recovery class is not active, the DR value indicates that when running in DR MODE, job requirements are automatically satisfied. In some cases, predecessor jobs never run in this particular disaster mode, and you want the requirement satisfied. The RQMTS=ALL option states that normal job requirement processing occurs.
Example: Default class and satisfied requirements
This example states that the default disaster recovery class is DR1 and that requirements are satisfied for jobs whose disaster class is not active.
DRMODE,DEFCLASS=DR1,RQMTS=DR
Example: Default class and normal processing
This example states that the default disaster recovery class for jobs without a DRCLASS designation is DR1 and that normal job requirement processing occurs.
DRMODE,DEFCLASS=DR1,RQMTS=ALL
The TRIGGERS= keyword is used to specify how trigger processing occurs during disaster recovery processing. The default TRIGGERS=DR mode indicates that only jobs with an active disaster recovery class are triggered. The TRIGGERS=ALL mode indicates that normal trigger processing occurs.
Example: Default class, normal processing, and some triggering
This example states that the default disaster recovery class for jobs without a DRCLASS designation is DR1. Normal job requirement processing occurs. Only jobs with an active disaster recovery class are triggered.
DRMODE,DEFCLASS=DR1,RQMTS=ALL,TRIGGERS=DR
Starting with r11.3, you have another option for triggering: TRIGGERS=NONEXEC. This setting lets triggered jobs process through the CA WA CA 7 Edition queues as nonexecutable if a job is in an inactive DR class. This setting permits the full job stream to enter the queue but only executes the active DRCLASS jobs.
The VERIFY keyword on the DRMODE statement lets operators confirm a disaster recovery mode startup. If CA WA CA 7 Edition is started with the DRMODE=YES EXEC parameter and the DRMODE initialization file statement includes the VERIFY=YES keyword, a WTOR is issued to allow for the confirmation of the disaster mode startup. The default is VERIFY=NO.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|