While performing a DR exercise, how do you release specific events while keeping all other groups on hold?
search cancel

While performing a DR exercise, how do you release specific events while keeping all other groups on hold?

book

Article ID: 51283

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

Description:

At your Disaster Recover exercise, you need to manually control the jobs/events that run. You do not code CLASS in the event definition so the EVENT prefixes will be used as the default CLASS. How do you release specific events while keeping all other groups on hold?

 

Environment

Release: ESP Workload Automation 

Cause

Need to control workload during a Disaster Recovery exercise.

Resolution

Solution:

Use the following procedure:

(Note - TEST is used here as an example of a group prefix. You will need to supply your own group prefix name.)

  1. First, you need to hold/suspend all classes as follows:
    OPER CLASS - SUSPEND/HOLD

  2. When you are ready to release a specific class, you want to exempt it from the hold/suspend:
    OPER CLASS TEST EXEMPT

    All events in this class, group TEST, will now be ready to trigger.

  3. When you are ready to run your schedules, you will need to release/resume all classes (group prefixes) as follows:
    OPER CLASS - RESUME/RELEASE

  4. You will want to unexempt the class that you previously exempted. If you do not do this step, it causes no impact but we recommend you unexempt as follows:
    OPER CLASS TEST DEEXEMPT

Additional Information

Holding an event is different from suspending it.

SUSPEND:
If the scheduled time for an event comes up while it is in the suspended state, the event execution is bypassed, and it is not considered overdue.

HOLD:
If the event is in a held state, it is placed in an overdue status. When the event is finally released, the overdue count is checked to see whether execution should proceed.

The event is checked immediately for every occurrence missed while in the held state, up to the overdue limit count specified when the event was defined.
If an event is in both a suspended and hold state when due for scheduling, the hold state is ignored, and the event is considered suspended.
The HOLD command is used with the RELEASE command. The SUSPEND command is used with the RESUME command.