Scheduling and calendar dependencies
When objects are defined to TOM with no schedule, TOM tries to maintain an object as ACTIVE (or available) 24 hours a day, 7 days a week.
To define when TOM takes an object out of ACTIVE status, you can specify a schedule as part of the object’s definition on the object ADD or EDIT dialog that is described in Creating-and-managing-objects.
You can also create calendar dependencies for other object attributes or properties, such as
- START and STOP retry commands for an object
- EXECs that are associated with starting or stopping an object
When you are defining these object properties, for example, you can instruct TOM to issue the START or STOP retry command, or to schedule any of the associated EXECs based on the date or time of day.
To simplify scheduling and calendar dependencies, TOM provides the ability to define calendar entries in one or more calendar definition bases (TCALENT view). With calendar definition bases, you can create dates and times (called calendar entries) and use them in an object’s Schedule dialog, or use them wherever calendar dependencies are allowed for the other eligible object properties (such as pre-start commands).
To define a one time exception of the schedule for an object, for maintenance or other reasons, you can specify Calendar Override. To learn more about defining a schedule, see Entering-calendar-dependencies.
For a complete discussion of calendar definition bases including examples for how to use calendar entries as part of the object’s definition, see Creating-a-new-calendar-definition-base.