ADVDD – Variable values for operation

Use the ADVDD statement to define variable values applicable to the operation instances that are generated by the specified run cycles.

Note: The ADVDD statement is available only starting from HCL Workload Automation for Z V9.3, or later.

Table 1. Keywords for ADVDD
Keyword	Description
`CRIT`	Specifies a variable job critical indicator to be associated with a variable run cycle: `N` Not eligible for WLM assistance. `P` Critical Path target. `Y` Eligible for WLM assistance.
`DLDAY`	Relative deadline day (00-99).
`DLTIME`	Deadline time (HHMM).
`DURATION`	Estimated duration for this run (in seconds).
`MH`	Specifies a variable `MH` (Manually Hold) option to be associated with a variable run cycle: `Y` The `MH` option is set to `Y` in the AD database that is associated with the related variable duration and deadline run cycle. `N` The `MH` option is set to `YN` in the AD database that is associated with the related variable duration and deadline run cycle.
`NOP`	Specifies a variable `NOP` option to be associated with a variable run cycle: `Y` The NOP option is set to Y in the AD database that is associated with the related variable duration and deadline run cycle. `N` The NOP option is set to N in the AD database that is associated with the related variable duration and deadline run cycle.
`RCGROUP`	Run cycle or run cycle group name to which you associate the variable duration and deadline.
`VACTIONACT`	Specifies the action to be taken if the operation has not yet started when the specified day and time is reached. If you specify an action, `VACTIONDD` and `VACTIONDT` are required. Allowed 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` The operation and all its internal successors are NOPed, if their status allows NOPing. Otherwise it is ignored.
`VACTIONBASE`	Always `F`. It means that the input arrival time of the operation is used as the base date to apply the offset.
`VACTIONDD`	Specifies the day offset, related to the application start day, used to check if the operation has not yet started. If the operation has not started, the action that you set is taken. It can be a value from 0 to 99 (where 0 means the start day, 1 means one working day after the start day, and so on). This overrides the default value.
`VACTIONDIR`	Always `A` (After). It means that the day offset and time are always added, and never subtracted, to the base date.
`VACTIONDT`	Required if you have set `VACTIONDD`. Specifies the time, related to the application start day, used to check if the operation has not yet started. If the operation has not started, the action that you set is taken. This check is made only to operations with status Ready. This value is specified in the format HH.MM. It overrides the default value.
`VALERTBASE`	Always `F`. It means that the input arrival time of the operation is used as the base date to apply the offset.
`VALERTDD`	Specifies the day offset, related to the application start day, used to check if the operation has not yet started. If the operation has not started, an alert message is issued. This check is applied only to operations with status Ready. It can be a value from 0 to 99 (where 0 means the start day, 1 means one working day after the start day, and so on). This overrides the default value.
`VALERTDIR`	Always `A` (After). It means that the day offset and time are always added, and never subtracted, to the base date.
`VALERTDT`	Required if you have set `VALERTDD`. Specifies the time, related to the application start day, used to check if the operation has not yet started. If the operation has not started, an alert message is issued. This value is specified in the format HH.MM. It overrides the default value.
`VDLACT`	Specifies the action to be taken if the operation is still not completed when the deadline day and time is reached. Blank means no action. If you specify an action, an alert message is always issued. Allowed 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 ODEA, if its status allows it. Otherwise it is ignored. `N` The operation and all its internal successors are NOPed, if their status allows NOPing. Otherwise it is ignored.