Entering calendar dependencies

By default, when no calendar dependencies are defined as part of the object’s definition in the Schedule field, TOM will always try to maintain the object’s status as ACTIVE. In addition, if you do not specify any calendar dependencies for the other six fields, TOM also always tries to take the actions specified in these fields (such as schedule any defined EXECs or issue any defined START or STOP RETRY commands).

When you enter a calendar dependency for the Schedule field or as part of the object definition for the other fields, TOM checks and evaluates the time entries that you specified. TOM processes the object definition, and events such as scheduling an EXEC associated with the object or issuing additional START or STOP RETRY commands are based on the times in the Schedule or Calendar Dependency fields.

Note

The discussion focuses on how to define calendar dependencies for the Schedule dialog, although the information is also valid for all other object attributes where calendar dependencies can be specified.

After you have analyzed the required availability schedule for the objects that TOM will manage, you can use the fields described in the following table to create calendar entries that meet your needs:

Calendar entry fields

Field	Description
Schedules	Specify when an object should be active or inactive.
Pre-start commands	Specify a command prior to starting the object.
Post-start commands	Specify a command after starting the object.
Pre-stop commands	Specify a command prior to stopping the object.
Post-stop commands	Specify a command after stopping the object.
Start retry commands	Specify start attempts with additional retry commands.
Stop retry commands	Specify stop attempts with additional retry commands.
Calendar Overrides	Specify one-time exception to the object's schedule, which can be used for system maintenance, and so on.

For each of these object properties, you can specify a calendar dependency on the dialog where you specify the name of a command that is associated with the starting or stopping of an object (or where you enter any additional object START or STOP RETRY commands).

This calendar dependency means that the specified RETRY command can be further defined to occur based on the day, period, time, or set calendar base definitions or at a single specific date and time.

To define periods of time when an object should be ACTIVE or STOPPED

Type E (edit) next to Schedules on the object ADD or EDIT dialog and press Enter.

The Object Management Calendar Dependencies dialog is displayed.

ADD or EDIT Schedules: calendar dependencies dialog

                 Object Management Calendar Dependencies
 COMMAND ===>                                              SCROLL ===> PAGE

  Sysplex: BBPLEX01   DefBase: DEFAULT
                      CalBase: DEFAULTCAL
  Object:  NEWOBJECT
  Product: Started Task Management

 Line commands: Edit, DELete, Up, Down, Top, Bottom

  Include logic: S AND   OR

 CMD I T Schedule Statement (partial)
 --- - - ---------------------------------------------             

                                                                              
 ADD - Add new schedule                                                      
 MERGE - Merge inherited records                                             
 END                                                                         
 CANcel                                                                      
 Help

In the Include logic field, specify AND or OR. The default value is AND.

On the Command line type AND or OR and press Enter.

The Specify Calendar Dependency dialog is displayed.

Specify calendar dependency

Specify Calendar Dependency
 COMMAND ===>                                              SCROLL ===> PAGE

  Sysplex: BBPLEX01   DefBase: DEFAULT
                      CalBase: DEFAULTCAL
  Object:  NEWOBJECT
  Product: Started Task Management

 Specify Calendar Dependency Information
 Type:   Include   Exclude

 During named
     Day:                      (Enter ? to select from list)
  Period:                      (Enter ? to select from list)
     Set:                      (Enter ? to select from list)
    Time:                      (Enter ? to select from list)

 From named                 To named
     Day:                           Day:
  Period:                        Period:
    Time:                          Time:

 From specific
  Date:                  Time:            ( ddmmmyyyy hh:mm )
 To specific
  Date:                  Time:            ( ddmmmyyyy hh:mm )

 END
 CANcel
 Help

The following table describes the fields for entering a calendar dependency on the Calendar Dependency dialog.

Fields for entering a calendar dependency

Field name or section	Valid values and definition
Type	You must select either Include or Exclude. Specify Include when the object should be ACTIVE during the specified times. Specify Exclude when the object should be STOPPED during the specified times.
You can make an entry in only one of the three sections of the dialog: During named From named — To named From specific — To specific Note The only exception to this rule is that you can specify a day entry in the During named section with From specific — To specific to allow for compatibility for those who are converting calendar definitions from the MainView AutoOPERATOR Continuous State Manager application.
During named	(optional) In this section, you can enter only one named entry for the Day, Period, Set, or Time fields. These named entries must be predefined in the currently active calendar definition base. Place a question mark (?) in the Day, Period, Set, or Time fields and press Enter to view a list of the currently defined named entries from which you can select.
From named — To named	(optional) In this section, you can enter a starting time (From named) and ending time (To named) by using previously defined period, day, or time entries. You cannot enter mixed pairs of entries such as entering a period for the From named and a time for the To named fields.
From specific — To specific	(optional) In this section you can specify dates and times in the following combinations: From specific, Date and Time and To specific, Date and Time From specific, Date and To specific, Date (no time specified) From specific, Time and To specific, Time (no date specified)This requires During Day or Specific Date.

After each calendar dependency is entered, the Schedule Calendar Dependencies dialog shows whether you entered an Include or an Exclude definition. If you entered Include, you must also specify AND or OR in the Include logic field.

AND	Signifies that if all time specifications are true, TOM tries to start the object and make the status ACTIVE for Type Include or STOPPED for Type Exclude.
OR	Signifies that if at least one Include specification is true, TOM tries to start the object and make the status ACTIVE for Type Include or STOPPED for Type Exclude. If the value of the Include schedule is a subset of the Exclude schedule then TOM will not start the object and the status will be STOPPED.

Entering calendar dependencies

To define periods of time when an object should be ACTIVE or STOPPED

Comments