Job Groups (JOBG)

A Job Group is a container for other objects. It helps you manage the execution of the individual objects it contains. As a developer and object designer, you use Job Groups to assemble individual objects that you want to execute collectively, either simultaneously or one after another. Job Groups can be stand-alone objects that you execute manually or you can insert them in Schedules or Workflows.

The objects included in a Job Group are flagged as belonging to a group. When you execute the group, it is displayed in the Process Monitoring perspective and its status is Active. The individual objects in the group are in Registered status first, and then Active as soon as they are executed.

When you execute objects that belong to a group from outside that group, their status remains as Registered. They are not executed unless the group is started as well.

Exception: When the individual objects are started by a Workflow, Schedule or a Recurring Task (C_PERIOD), the Job Group setting in the object definition is ignored.

Job Groups do not have object-specific pages since they are mere containers for other objects.

You assign a Job to a Job Group on the Attributes page of the Job.

A Job Group definition is made up of the following pages:

Execution Sequence of the Jobs in the Group

Specify the number of Jobs that the group can execute simultaneously in the Runtime Parameters section on the Attributes Page of the Job Group definition:

Next Steps

See also: