Creating job definitions

How to define a new job definition using the Dynamic Workload Console.

About this task

From the Workload Designer panel of the Dynamic Workload Console, you can define multiple types of jobs, running on both distributed and z/OS® environments. Most of them can also be created using composer (on distributed systems) and ISPF (on z/OS® systems) interfaces. Some predefined job types are organized into categories including native jobs, and job types with advanced options, which are specific job types that you use to perform operations on external applications. In addition to the existing ones, you can define your own job types and add them to this list or organize them in smart workflow folders. To create a new job definition from the Dynamic Workload Console, perform the following procedure:


  1. From the navigation toolbar, click Design > Workload Definitions > Manage Workload Definitions
  2. Specify an engine name, either distributed or z/OS®.
    The Workload Designer opens. Job types and characteristics vary depending on whether you select a distributed or a z/OS® engine.
  3. In the Create New pane, select Job Definition.
  4. Select the category and type of job you want to create.
  5. In the properties panel, specify the attributes for the job definition you are creating. For all the details about available fields and options, see the online help by clicking the "?" on the top-right corner.
  6. Click Save to save the job definition in the database.


When you define a job, HCL Workload Automation records the job type in the database without performing further checks. However, when the job is submitted, HCL Workload Automation checks the operating system on the target workstation and defines the job type accordingly.

Optionally, if you are connected to a distributed engine, you can quickly submit the job definition into the current plan to be run. You might want to do this for testing purposes before implementing the job in large-scale production. See Quick submit of jobs and job streams.

Once job definitions have been submitted into the production plan, you still have the opportunity to make one-off changes to the definitions before they run, or after they have run. You can update the definition of a job that has already run and then rerun it. The job definition in the database remains unchanged.

For more information about creating the plug-ins to support the definition and running of dynamic job types, see HCL Workload Automation Developer's Guide: Extending IBM Tivoli Workload Automation