Before you add an IMS data map, you must gather information about the IMS database.
Gather the following information about the IMS source or target:
The IMS SSID, which is required for ODBA access and IMSUNLD access to unload files.
The IMS database name and database data set name.
The DBD data set name and location.
The PSB name.
If you use IMS DL/I batch or BMP access to IMS data, determine the PCB number by counting the number of PCBs in the PSB. If the PSB has COMPAT=YES, add one to that number.
If you use IMS ODBA access, record the PCB name.
The names of the IMS segments, and which segments, if any, are of variable length. Additionally, note the hierarchical sequence as defined in the DBD source.
To reduce the number of locking conflicts, set PROCOPT to read-only for the PCB for the IMS database.
If the PSB is used with the IMS ODBA interface or a Netport BMP job, define the PSB in the IMS SYSGEN.
Update the DBMOVER configuration member in the RUNLIB library.
Update the dbmover.cfg configuration file on the PowerExchange Navigator system.
If you plan to perform INSERTs or UPDATEs on an IMS segment, the data map must represent the complete segment length as defined in the IMS DBD. Otherwise, an INSERT or UPDATE to the segment might write nonblank data to the end of the segment not defined as FILLER. To avoid this issue, you can add a FILLER definition to the COPYLIB before you import it to PowerExchange.