Optimizing the workload through a smooth submission of the operations
You can better balance the submission of operations by prioritizing the jobs that are urgent (with priority 9) or that belong to a critical path; furthermore, you can add a delay to the submission of the remaining operations.
As normal behavior, HCL Workload Automation for Z submits
the operations in plan as soon as possible. Under certain circumstances, this might lead to a system
overload and job interlock. By combining the following settings in JTOPTS and BATCHOPT you can tune
the scheduling as best fit to your network.
- JTOPTS
- You are provided with the following parameters:
- SMOOTHSUBMISSION
- Activates the Smooth Submission feature. By setting this parameter to YES, the submission of
operations that are urgent (with priority 9) or belong to a critical path is prioritized.
Moreover, if you set the SMOOTHSUBCONFLEVEL and SMOOTHSUBDELAY parameters in the BATCHOPT statement, the controller adds a random delay in submitting not urgent and not critical operations.
- SMOOTHCRITNET
- By setting this parameter to YES, the submission of the operations belonging to the whole critical network is prioritized. This setting is meaningful if SMOOTHSUBMISSION is set to YES.
- SMOOTHSUBRATE
- The average number of operations to be submitted, in 1 minute, on computer automatic
workstations, with the exception of the operations that are urgent (with priority 9).
If you also set SMOOTHSUBMISSION(YES) and SMOOTHCRITNET(YES) to prioritize the operations that are urgent and the operations that belong to a critical network, these operations are not affected by the submission rate restrictions.
- BATCHOPT
- You are provided with the following parameters:
- SMOOTHSUBDELAY
- Based on this setting, the controller adds a random delay in the submission of operations that are neither urgent, nor belonging to a critical path. It is expressed in seconds; the default is 0, meaning that no delay is added. Regardless of this value, the operation latest start time is never exceeded.
- SMOOTHSUBCONFLEVEL
- A value used to calculate the submission delay added by SMOOTHSUBDELAY. This is useful to prevent that the delay causes an operation submission too close to its latest start time.
For more details about the statements, see JTOPTS and BATCHOPT.
The following example shows how to prioritize the submission of operations that are urgent and
those that belong to a critical network. By setting SMOOTHSUBRATE(nnnn), you also ensure that
all the other operations follow a constant scheduling during the plan execution. The value for
nnnn depends from the volume of your current plan, and its execution
window.
JTOPTS
SMOOTHSUBMISSION(YES)
SMOOTHCRITNET(YES)
SMOOTHSUBRATE(nnnn)