Navigator User Guide

10.5.5
- 10.5.6
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

IMS Data Maps

To use an IMS database as a data source or target, define an IMS data map. The data map is required to create SQL statements for relational-type access to IMS data during session processing.

When creating the data map for an IMS source or target database, add one or more IMS segments, and the fields in the segments, to define the physical layout of the data. A data map also includes table views of the data. The segment and field definitions provide the nonrelational view of the data, and the tables and columns provide the relational view of the data.

For IMS data sources, record
refers to a root segment and its children.

A data map can include one segment or multiple segments:

Define a single segment in a data map if the associated data file contains one segment type. A single-segment data map can define multiple tables.

Define multiple segments in a data map if the source database contains multiple segment types. The fewer columns that PowerExchange must retrieve results in faster file processing and data extraction.

You can use data maps to align fields, convert dates, filter data, and enhance data to improve data accuracy and reduce data volume. You can also use data maps for Lookup transformations that look up related values and determine if rows exist in an IMS target.

To define an IMS data map, complete the following tasks:

Add an IMS data map.

When you define the data map, select the

DL/1 BATCH

IMS ODBA

access method and associate the data map with a data file that defines the record types and data. You must also enter the IMS source or target properties that the access method requires. DL/I batch access requires a PCB number. ODBA access requires an IMS SSID, PSB name, and PCB name.

You can override the access method in the data map when you configure a PowerCenter session or perform a database row test. If you override the access method, you must also enter the properties that the new access method requires.

If the DBD source is available for the IMS data, import the DBD source into the data map.

The DBD source defines segments and the hierarchical sequence for the data map. During the import process, PowerExchange maps the IMS segments and fields to tables to create the relational view of source data that PowerExchange requires.

To overlay each segment with its COPYLIB, import a COBOL copybook into each IMS segment in the data map.

Send the data map to the PowerExchange Listener on the local or remote node to store the data map in PowerExchange.

This action converts the data map into an operating-system-independent file that PowerExchange can access for extraction processing.

Run a database row test to test the data map.

A database row test accesses actual source data, displays it in table format, and verifies that you can access data from the source database.

The PowerExchange installation includes the example IMSDEMOS file that includes a example IMS DBD source that you can use to create a example IMS data map.

Data Maps for Specific Data Sources

Prerequisites for Adding an IMS Data Map

Configuring DL/I Batch or BMP Access to IMS Data

Configuring IMS ODBA Access to IMS Data

Configuring the PowerExchange dbmover.cfg File on Windows

Adding an IMS Data Map

Viewing IMS Data

Viewing an IMS Hierarchy

Adding Expressions to an IMS Record

Getting the RBA for an IMS Record

Editing Properties in an IMS Data Map

Sending an IMS Data Map to a Remote System