HP Archive Backup System for OpenVMS Guide to Operations

Saving and Restoring Data
3.7 Schedules
3.7 Schedules
3.7.1 After Schedule
ABS supports very flexible options for scheduling save and restore requests, both using the
internal MDMS scheduling options and using a third part scheduler. The scheduling options can
be divided into three main categories:
• Standard - ABS provides a list of standard options that you can specify, and the scheduling
information is applied to the schedule object automatically. Standard options are supported
by both internal MDMS scheduling and an external scheduler product. Standard options are
all those that are neither custom or explicit.
• Custom - This option allows you to customize the schedule for the request if the standard
options are not sufficient. For example, if you want to run the request every second Sunday
in January, April, July and October, then the custom option can do this. You specify CUS-
TOM as the frequency, then modify the schedule object for the request directly. This option
is applicable to internal MDMS scheduling only.
• Explicit - This option also allows you to customize your schedule, but this time with an
external scheduler product. You specify EXPLICIT as a frequency, then enter a string into
the EXPLICIT INTERVAL attribute. This attribute is a string that can be understood by the
external scheduler product specifying the desired frequency. Alternatively, you can use the
user interface of the external scheduler product to specify the frequency of the request. This
option is applicable only to external scheduling options.
This section discusses the second option, custom schedules, which are only applicable to internal
MDMS scheduling. To use a custom schedule, specify CUSTOM as the frequency on the save
and restore request, then modify the attributes of the associated schedule object. The schedule
object always has the name of the save and restore request, followed by “_SAVE_SCHED” or
“REST_SCHED” respectively.
With ABS custom scheduling, you can actually define one schedule to execute after another
schedule has completed. For example, if you want SAVE2 to execute immediately after SAVE1
completes, you can modify SAVE2’s schedule object and setting its AFTER SCHEDULE
attribute to SAVE1’s schedule object. In this case:
SAVE2_SAVE_SCHED:
After Schedule: SAVE1_SAVE_SCHED
If you specify an after schedule and only want the associated request to execute after the after
schedule (and not at any other time), then do not specify any other date or time attributes in the
schedule. If on the other hand you want the associated request to execute at regular times AND
after the specified after schedule, then you can associate date and time attributes to the schedule.
With after schedule, you can also define conditions upon which the schedule will run after the
other schedule. The conditions are stored in an attribute called after schedule when. Select from
one of the following:
• ALL - Always run the schedule after the dependent schedule completion
• SUCCESS - Run the schedule if the dependent save or restore completed with a successful
status
• WARNING - Run the schedule if the dependent save or restore completed with a Warning,
Error or Fatal status
• ERROR - Run the schedule if the dependent save or restore completed with an Error or
Fatal Status
3-32 Saving and Restoring Data