Tasks > Dynamic mapping tasks > Jobs and job groups
  

Jobs and job groups

A dynamic mapping task can include multiple groups of jobs. A job is a single run of the mapping that the task is based on. Add jobs to a dynamic mapping task and organize them into groups on the Jobs page. You can configure a different set of parameter values for each job.
Assign each job to a group. A group is a set of jobs that run concurrently. Groups run sequentially, and all jobs in the previous group complete before the next group begins. You might set up groups when data in one group depends on the results of a previous group. There is no limit on the number of jobs and groups that you can add to a dynamic mapping task.
The following image shows the Jobs page:
The image shows the Jobs page with three jobs and two groups. Job_1 is expanded and contains five parameters. The target object parameter is selected. Job_1 and Job_2 are in Group_1. Job_3 is in Group_2. All three jobs and both groups are enabled.
  1. 1Add a job
  2. 2Select parameter value
  3. 3Parameter settings
  4. 4Add a job to a group
  5. 5Enable/Disable job
  6. 6Add a group
When you add a job, Data Integration displays each parameter in the mapping. If a parameter has default scope, Data Integration automatically applies the default value to the job. You can edit the parameter value and parameter settings for each job.
By default, Data Integration enables a job or group when you add it. You can disable individual jobs so that they won't run when you run the task. If you disable a group, no jobs in that group run when you run the task.

Job settings

You can configure settings for each job including stopping the job on an error or warning, advanced session properties, and pre and post processing commands. Configure job settings in the Settings window.
When you set the Stop on property for a job that is in a group, if the job encounters the configured state, the jobs in the group complete, and then the task stops.
To configure job settings, click Settings in the row that contains the job.
You can optionally configure the max compute units and task timeout serverless usage properties for a dynamic mapping task job in a serverless environment. Maximum compute units and task timeout settings are configured for serverless environments in Administrator but you can revise their values for a particular dynamic mapping task job.
You can use the max compute units property to increase or decrease the number of compute units corresponding to the machine resources that a job can use based on the Max Compute Units Per Task serverless environment property value. You might want to specify a smaller value for a simple job, or a larger value for a complex job. The Max Compute Units property value for a dynamic mapping task must be less than or equal to the Max Compute Units Per Task value in the serverless environment.
You can use the Task Timeout property to increase or decrease the amount of time in minutes to wait for a job to complete before it is terminated based on the Task Timeout serverless environment property value.
For more information about the Max Compute Units Per Task and Task Timeout serverless environment properties, see Basic Configuration in the Administrator help.