You can write source data from a data map to an IMS database.
Use the PowerExchange Client for PowerCenter (PWXPC) to write data to IMS.
When you write data to IMS, consider the following guidelines:
Specify the key values of a segment so that all the processing required to write data for the segment occurs within IMS.
You cannot use SDEP segments.
You cannot update a segment below an unkeyed segment.
You can use segments that contain an OCCURS clause where the COPYLIB has been changed to identify each of the fields in the OCCURS clause as a separate field, which eliminates the OCCURS clause in the COPYLIB definition. You cannot generate a separate row for each occurrence of the OCCURS clause.
When you import a data map to PowerCenter, verify that any CCK fields that you want to use as key fields are marked as key fields.
In PowerCenter, use a lower Commit frequency to reduce the risk of locking segments.
Use a separate netport job to write IMS data. Using a separate netport job enables you to access a PSB with write intent and to modify the JCL to update IMS data, such as the IEFRDER log.
When you write data for one of the following types of fields to the database, indicate whether the field is optional when you add the data map:
Spaces to a field
No data to a field
If you have several fields of this type, indicate that the first field in the data map is optional, and that all fields following this field are optional. If you do not specify the field is optional, errors appear in the PowerCenter session log.
To verify that the z/OS system is accessible, ping the IP address of the z/OS system where the target database is located.
In the dbmover.cfg configuration file, include a NODE statement that points to the remote z/OS system.
To verify that the remote PowerExchange Listener is started, issue the following command:
dtlrexe loc=
xxxx
prog=ping uid=
userid
pwd={
password
|
passphrase
}
Where
xxxx
is the NODE name from the PowerExchange configuration file dbmover.cfg.
In the PowerExchange Navigator, add, test, and store an IMS data map.