Db2 for z/OS Connector > Mappings and mapping tasks with Db2 for z/OS Connector > Mapping configuration
  

Mapping configuration

You must configure a mapping that contains a Source transformation for a Db2 for z/OS source and map it to a Target transformation.
To begin creating a mapping in Data Integration, click New > Mappings > Mapping and then click Create. In the New Mapping dialog box, click Mapping > Continue.
When you define a Source transformation in a mapping, specify a name for the transformation, a Db2 for z/OS connection, the source type, and the table for the Db2 source object. You can also set some additional source properties. The PWX Bulk Metadata Adapter retrieves metadata for the source table from the Db2 database catalog.
A mapping must contain at least one Source transformation mapped to one Target transformation. Alternatively, a mapping can contain multiple Db2 for z/OS sources and multiple targets. For example, you can define multiple one-to-one mappings, map one source to multiple targets, or map multiple sources to one target. To map multiple sources to the one target, you can create multiple one-to-one mappings that map each source separately to the same target. In this case, each source must have a different primary key value.
When you define a Target transformation, specify a name for the transformation, a connection to the target and the target type. In the user's environment, the target can reside on premises or in a cloud. If you do not want to send all of the incoming fields to the target, you can define one or more exclusion field rules. As part of configuring the target, you must also map the incoming fields to the target fields. You can map fields automatically based on the field names or map them manually.
Instead of selecting specific connections and objects in the Source and Target transformations, you can define a parameter for the connection, the source or target object, or both. You then must enter a specific connection or object in the associated mapping tasks. If you want to use a parameter for the source or target connection, you must perform one of the following actions before the mapping can be successfully validated:
You can also completely or partially parameterize field mappings, and then define specific mappings in the mapping tasks.

Db2 for z/OS source properties in mappings

When you create a mapping, you configure a Source transformation for a Db2 for z/OS source and set some source properties for the Source transformation.
Click the Source transformation box on the mapping canvas. Then configure the source properties in the Source Properties panel below the mapping canvas.
If you have multiple Source transformations in a mapping, configure source properties for each source. If you use a specific connection instead of a connection parameter, enter the same connection for all sources.
Note: If a mapping includes source tables or columns that have special characters in their names, the associated mapping task fails because it cannot import the source metadata. Special characters include s #, $, @, %, *, !, and ~. Therefore, ensure that none of the source tables and mapped columns have names with any special character. Rename the tables and columns if necessary.
The Source Properties panel contains the following tabs on which you can enter information:
Note: Ignore the Partitions tab. Key-range partitioning is not supported.

Targets in mappings with Db2 for z/OS sources

To configure a target in a mapping, click the Target transformation box on the mapping canvas. Then configure the target properties in the Target Properties panel below the mapping canvas.
Note: To determine which target types are supported by the Db2 for z/OS Connector, see Supported targets.
In the Target Properties panel, enter information on the following tabs:

Lookup Transformation

You can configure a cached Lookup transformation when you use a Db2 for z/OS connection in a mapping to return data from a Db2 for z/OS source based on a specified lookup condition. However, the Db2 for z/OS Connector does not support uncached lookup.
For more information, see Cloud Data Integration Transformations.