HCL Workload Automation, Version 9.4

Submitting and tracking jobs

Although you should normally use the standard HCL Workload Automation means to schedule and submit workload, there is also an additional way to submit jobs directly to dynamic scheduling using either the Dynamic Workload Console or the HCL Workload Automation command line, described in the next chapter. This implies that you only need to write a JSDL job definition. You do not need to write a job definition in HCL Workload Automation and the workload broker workstation does not come into play. Choosing to do so, however, results in not exploiting the scheduling and choreography services of HCL Workload Automation. This chapter explains how to submit and track jobs using the Dynamic Workload Console.

About this task

Job definitions are stored in the Job Repository and you search for them and select them when the job needs to be submitted. At submission time, you can also specify that a job run on the same resource as a job that has previously run. The job definition provides all necessary parameters for a job to run, however, you can add to and change the parameters defined in the job definition for the job instance you are submitting. This does not change the job definition stored in the Job Repository.

The lifecycle of a job involves the following sequence of phases:

Using the Dynamic Workload Console, you can manage the whole lifecycle of a job by performing the following task: