Specifying times, actions, and alerts for operations

For each operation making up an application, on the TIME SPECIFICATIONS panel (EQQAMTMP - Time specifications ), which you can reach by selecting option 6 in the OPERATION DETAILS panel (EQQAMSDP - Operation details ), you can specify:

Input Arrival Time and Deadline. If you do not specify them, the input arrival time and deadline for the application are used.
Deadline Action. When specified, if the operation does not complete within the time that you set, an alert message is issued and the action taken.
Note: This setting is effective only if you set NOTSTARTCOMP(YES) in the JTOPTS initialization statement.
Valid values are:

‘ ’ (blank)

No action is taken.

A

Only an alert message is issued.

C

The operation is set to Complete, if its status allows it. Otherwise it is NOPed.

E

The operation is set to Error with ODEA, if its status allows it. Otherwise, this setting is postponed at the time when the status allows it.

N

Operation and all its internal successors are NOPed, if their status allows NOPing. Otherwise it is ignored.
Not Started Alert and Not Started Action. When specified, if the operation does not start within the time that you set, an alert message is issued and the action taken.
Note: This setting is effective only if you set NOTSTARTCOMP(YES) in the JTOPTS initialization statement.
Valid values are:

A

Only an alert message is issued.

C

The operation is set to Complete, if its status allows it. Otherwise it is NOPed.

E

The operation is set to Error with OLAT, if its status allows it. Otherwise, this setting is postponed at the time when the status allows it.

N

Operation and all its internal successors are NOPed, if their status allows NOPing. Otherwise it is ignored.
Variable values applicable to the instances generated by the specified run cycles.

Figure 1. EQQAMTMP - Time specifications

EQQAMTMP -------------------- TIME SPECIFICATIONS -----------------------------
Command ===>

Enter/Change data below:

Application time specifications:
 Input arrival time             :     10.00
 Default deadline day/time      : 00  20.00
 Default duration               :     00.02.00

Operation time specifications   :   CPUA 015
 Input arrival                  :   DAY   00    TIME  10:22
 Default operation deadline     :   DAY   00    TIME  18:00   ACTION  A 
 Not started alert              :   DAY   00    TIME  18:00    
 Not started action             :   DAY   00    TIME  18:00   ACTION  E

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

Row    Ext./Appl. Duration  Deadline         NOP  MH  Crt  Not Started  Not started 
cmd    Run Cycle  HH.MM.SS  DD  HH.MM   Act           ind  alert        action
                                                           DD  HH.MM    DD  HH.MM Act           
''''   MONTHLY_   ________  00  22.32   A    _    _   P    01  21.00    02  22.00 E
''''   WEEKLY__   ________  00  20.00   A    _    _   P    02  23.00    04  24.00 A

The day for the Input arrival, Deadline, Not started alert, Not started action is relative to the input arrival date for the occurrence. Specify a number from 0 to 99, where 00 means that the day is also the input arrival day. When the specified day is greater than 0, HCL Workload Automation for Z by default considers only work days when calculating the date. For example, if day is 1, this specifies the first work day (as specified by the calendar) after the input arrival date. You can change HCL Workload Automation for Z to include free days when calculating deadline dates.

Note:

If you run the DP batch with BATCHOPT IGNOREDEADL(YES), the critical path processing will always use the current plan tail end as the deadline for the operations that do not belong to a critical path or are not marked as Suppress if late.
For more information about the IGNOREDEADL parameter, see BATCHOPT.
In the BATCHOPT statement, you can also set the OPERIALL and OPERDALL parameters to determine, respectively, the operation input-arrival date and deadline date.
When you use the Modify Current Plan (MCP) panel, consider that the action that you set as Deadline Action or Not Started Action, is taken only once for an operation. This means that any changes you make to the operation (for example, you change its status from Error to Ready) does not imply that the action that was already taken is performed again.

Specify the following variable values when your operation, in specific days, needs values different from the default. Then associate an application run cycle or run cycle group with the variable values that you set.

Duration: Duration of the operation.
Deadline: Deadline day offset and time for the operation to complete, related to the application start day.
NOP: NOP option for the operation.
Manually Hold: Manually Hold option for the operation.
Critical Indicator: Critical indicator for the operation.

For example, you have an operation that runs every day with the same duration, except on Fridays and on the last day of month. You can do either of the following actions:

In the application definition, define three run cycles in this order: for the last day of month, for Friday only, for every day (the order is important because in case of time overlapping, the run cycles are applied in the order they are listed). In the TIME SPECIFICATIONS (EQQAMTMP) panel , associate the required variable duration with each run cycle that you defined for the application.
In the application definition define only one run cycle, which is related to the every day run. Then define two run cycle groups, which you reference in the AD database, related to occurrences running on Fridays and occurrences running on the last day of month. According to the time needed by the specific occurrences, in the TIME SPECIFICATIONS (EQQAMTMP) panel associate a variable duration with each of the two run cycle groups.