Creating the default calendar

About this task

A calendar in HCL Workload Automation for Z defines the status of each day and the workday end time. HCL Workload Automation for Z uses the calendar when it creates the long-term plan. When it creates the current plan, and when it decides whether to submit work, it does not refer to the calendar, so you cannot use the calendar to close down a system at short notice. Instead, change the workstation open intervals by using the MODIFY CURRENT PLAN panel, as described in Changing workstation availability.

To create the default calendar:
  1. Select option 1.2.2 from the HCL Workload Automation for Z main menu.
  2. You see a list of calendars, if any exist. You can modify an existing calendar or to create a new calendar, enter CREATE at the command prompt. The CREATING A CALENDAR panel (EQQTCCAL - Creating a calendar ) is displayed.
    Figure 1. EQQTCCAL - Creating a calendar 
     EQQTCCAL -------------------- CREATING A CALENDAR ---------- ROW 1 TO 20 OF 35
 Command ===>                                                  Scroll ===> CSR

 Enter/change data below and in the rows,
 and/or enter any of the following row commands:
 I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - Delete

 CALENDAR ID        ===> default______
 DESCRIPTION        ===> lots and lots of holidays_____
 WORK DAY END TIME  ===> 00.00

 Row  Weekday or     Comments                       Status
 cmd  date YY/MM/DD
 '' SUNDAY________ ______________________________   F
 '' MONDAY________ ______________________________   W

 '' 03/05/05______ Spring May Holiday - UK_______   F
 '' 03/06/21______ Midsummer's Day - Sweden______   F
 '' 95/07/01______ Canada Day____________________   F
 '' 95/07/04______ US Independence Day___________   F
  3. Type DEFAULT for the calendar ID.
  4. Enter W for the status of the days of the week that are work days, and F for the non-work days and holidays. A day is specified as either:
    Work day
    When HCL Workload Automation for Z schedules work as normal
    Free day
    When HCL Workload Automation for Z plans work according to the free-day rule on each application run cycle. For detailed information about the free-day rule, see Selecting a free-day rule.

    The status specified for a particular date overrides the specification for the corresponding day of the week.

  5. Specify the workday end time. If your installation shuts down, it probably does not do so at midnight. Normally, a system shuts down at the end of a shift, for example 6 a.m. This could be considered as the workday end time for your installation: the time that a normal work day ends. The workday end time is the time of day that a work day ends and a free day begins, and is the time of day that a free day ends and a work day begins, but be careful if you specify a time before midnight: the work day after a free day starts at the first workday end time on the work day. If the workday end time is after midnight, the workday end time determines when work is planned to run. If the workday end time is before midnight on the free day, HCL Workload Automation for Z waits for the next workday end time: the one on the work day after the free day, which is probably not what you expect, so it is recommended that you specify a workday end time at 00.00 or a later time.
    Note: Specify all times of day in 24-hour notation: never use a.m. and p.m.
    Example 1: the workday end time is 02.00, and Saturday and Sunday are free days
    • The long-term plan (LTP) has work until 02.00 Saturday morning.
    • There is no work in the long-term plan starting between 02.00 Saturday morning and 01.59 Monday morning, unless the free-day rule in the run cycle specifies that the application can run on a free day.
    • Work for Monday begins at 02.00 Monday morning.
    • Run cycles that specify an input arrival time between 00.00 and 01.59 generate an occurrence on the following day. For example, the rule Every Monday in the Year generates occurrences early on every Tuesday morning (taking the free-day rule into account if Monday is a free day).

    Example 2: the workday end time is near midnight

    In this example, Sunday is a free day and Monday is a work day. Assume that the free-day rule in the run cycle specifies that no applications are run on free days.

    End time
    Effect on scheduling
    00.00
    No applications will be scheduled to run on a Sunday. Applications scheduled to run on Monday will start just after midnight between Sunday and Monday.
    00.01
    The Sunday free day runs from 00.01 on Sunday to 00.00 (midnight between Sunday and Monday) inclusive. If you specify a day with an input arrival time of 00.00 on the run cycle, HCL Workload Automation for Z assumes that you mean midnight between that day and the next day—times before the workday end time come at the end of the work day.
    23.59
    This work day end time is not recommended. The free day, Sunday, starts at 23.59 on Sunday and ends at 23.59 on Monday. The following work day, Monday, starts at 23.59 on Monday and lasts for 1 minute. In other words, almost no applications would be scheduled for Monday.
    24.00
    This work day end time is not recommended. The work day, Monday, would be lost because the start of the day would be midnight between Monday and Tuesday.

    The workday end time has no effect on the daily planning process; when HCL Workload Automation for Z creates the current plan, it is the workstation open hours that determine if work will start within a particular period. If you do not want HCL Workload Automation for Z to plan or start work on a free day, close all workstations. If workstations are open on a free day, operations that have not finished processing by the workday end time will continue to process on the free day.

When you use an extra calendar , specify the calendar name for the application, job, or group definitions that do not use the default calendar.

When you modify the current plan using the ETT, ARC, or PIF, the subsystem has no access to the OPTIONS panel calendar name, or to the calendar specified in the BATCHOPT initialization statement. Unless you explicitly specify a calendar in the application description, the subsystem tries to use the calendar called DEFAULT. It is strongly recommended that you use the name DEFAULT for your normal calendar.