HCL Workload Automation, Version 9.4

Promoting jobs scheduled on dynamic pools

This section explains how to promote a critical job scheduled on a dynamic pool. A promoted job can run on a larger number of dynamic agents in the dynamic pool than a non-promoted job. This ensures that an important job runs before other jobs that are less important.

To ensure that a critical job obtains the necessary resources and is processed in a timely manner, specify the following variables:

tws.job.promoted: This variable indicates if the job is promoted. Supported values are YES and NO. The value of this variable applies to all jobs submitted in the specified environment.
tws.job.resourcesForPromoted: This variable is defined in the dynamic pool definition and indicates the quantity of the required logical resources assigned on a dynamic pool to a promoted job. Values can be 1 if the job is promoted or 10 if the job is not promoted. The quantity is indicated with this notation: ${tws.job.resourcesForPromoted}.

When a job is scheduled on the dynamic pool, the value of the tws.job.promoted variable in the job determines the behavior of the dynamic pool:

If the value of the tws.job.promoted variable is NO, the value of the tws.job.resourcesForPromoted variable on the dynamic pool is 10, which means that few resources match the requirement.
If the value of the tws.job.promoted variable is YES, the value of the tws.job.resourcesForPromoted variable on the dynamic pool is 1, which means that more resources match the requirement because the dynamic pool includes workstations with resource quantity equal to or greater than 1 and not only workstations with value equal or greater than 10.

For example, you can write a script that checks the value assigned to the tws.job.promoted variable in the job and performs different actions based on whether or not the job is promoted.