Defining a job

Define HCL Workload Automation jobs to run business tasks and processes defined in an external application.

Define your HCL Workload Automation job to run tasks or processes you have defined in external applications. Using the HCL Workload Automation job plug-in for your external application, you can define, schedule and run jobs to automate your business.

In distributed environment, define a job by using the Dynamic Workload Console connected to a distributed engine, by using the composer command line.

In a z/OS environment, define a job by using the Dynamic Workload Console connected to a z/OS engine.

How to define a job using the Dynamic Workload Console

For details about defining jobs from the Dynamic Workload Console, see Creating job definitions.

How to define a job using the composer command line

The composer command line supports the following syntax when defining a job:

$jobs
[[folder/]workstation#][folder/]jobname
   {scriptname filename  streamlogon username |
     docommand "command" streamlogon username |
     task job_definition }
   [description "description"]
   [tasktype tasktype]
   [interactive]

   [succoutputcond Condition_Name "Condition_Value"]
   [outputcond Condition_Name "Condition_Value"]

[recovery
{stop
[after [[folder/]workstation#][folder/]jobname]
[abendprompt "text"]]
|continue
[after [[folder/]workstation#][folder/]jobname]
[abendprompt "text"]]
|rerun [same_workstation]
[[repeatevery hhmm]  [for number attempts]]
[after [[folder/]workstation#][folder/]jobname]
|[after [[folder/]workstation#][folder/]jobname]
[abendprompt "text"]}

Use the task argument, specifying the XML syntax for the specific job plug-in. See the section for each job plug-in for the specific XML syntax.

For a detailed description of the XML syntax, see Job definition.

For some jobs a properties file can be generated and used to provide the values for some of the properties defined in the job definition.

The properties file is automatically generated either when you perform a "Test Connection" from the Dynamic Workload Console in the job definition panels, or when you submit the job to run the first time. Once the file has been created, you can customize it. This is especially useful when you need to schedule several jobs of the same type. You can specify the values in the properties file and avoid having to provide information such as credentials and other information, for each job. You can override the values in the properties files by defining different values at job definition time.