Information about jobs, which are scheduling objects used to define and run activities in the scheduling environment.

A job is a unit of work that specifies an action, such as a weekly data backup, to be performed on specific workstations in the HCL Workload Automation network.

In a HCL Workload Automation distributed environment, jobs can be defined either independently from job streams, within a job stream definition or in smart workflow folders.

In a HCL Workload Automation for z/OS environment, jobs can be defined only within a job stream and are called operations. You can have started-task operations, which are operations run on a computer workstation that are used to start and stop started tasks.

Regardless of whether the HCL Workload Automation engine is distributed or z/OS based, you can define locally a shadow job to map a remote job instance running on a different HCL Workload Automation engine.

For more information about the job definition, see Defining scheduling objects.

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.