Understanding availability intervals

Before you use the Special Resource Monitor, be sure that you understand how availability intervals work. How attributes are preserved across intervals shows how planned availability is affected by unplanned events such as input from the Special Resource Monitor, the SRSTAT command, and the EQQUSIN subroutine. Notice that manually altered attributes are honored across an interval boundary and batch planning EXTEND and REPLAN jobs; to make HCL Workload Automation for Z revert to the scheduled values after a manual alteration, you must reset the attribute, as at 11.20 in How attributes are preserved across intervals.

Table 1. How attributes are preserved across intervals
Planned valuesActual values
Start of interval / time of eventPlanned quantityPlanned availabilityActual quantityActual availabilityDeviation Number available
08.008NInterval specifies quantity 8, not available
8N0 0
08.40You set the availability to Y with the EQQUSIN subroutine
8 Y08
09.00 8NA new interval specifies the resource unavailable
8 Y08
09.40 You set a deviation of -1 with the SRSTAT command
8Y-1 7
09.41You set a deviation of -1 with the SRSTAT command
8Y-2 6
09.42You set the deviation to -1 with the Special Resource Monitor
8 Y-17
10.00 9YExtend CP, and interval specifies 9 available
9 Y-18
10.20 You set the quantity to 6 with the SRSTAT command
6Y-1 5
11.008Y Interval specifies 8 available
6Y-1 5
11.20You reset the quantity with the SRSTAT command
8Y-1 7

The number available (the last column) is the actual number available for allocation, taking into account the actual quantity, the deviation, and the actual availability.

The three events starting at 09.40 show the difference between altering the deviation with SRSTAT (or a subroutine) and with the Special Resource Monitor. SRSTAT adds the specified deviation to the current deviation, but the panel replaces the current deviation with the value you specify.

If you change values other than the overriding (global) quantity, availability, and deviation, or the values for an interval, you lose the changes at the next daily planning run, but the job issues a warning message about any manually changed values that will be lost. For example, if you change the default quantity (the quantity used where intervals are not specified) in the current plan, this is replaced at the next daily planning run with the value from the database.