Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.4.0
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMXLUTL - Event Marker Utility
  18. HOSTENT - TCP/IP Address Reporter Utility
  19. PWXCATMY - MySQL Catalog Utility
  20. PWXUCCLPRT - Print Log Summary Utility
  21. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  22. PWXUCREG - Capture Registration Suspend Utility
  23. PWXUCRGP - Capture Registrations Print Utility
  24. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  25. PWXUGSK - SSL Reporting Utility for z/OS
  26. PWXUMAP - Map List Utility
  27. PWXUSSL - PowerExchange SSL Reporting Utility

Utilities Guide

Utilities Guide

Back Next

Copying IMS Data Maps and Registrations and Modifyng the IMSID Data Map Property

Copying IMS Data Maps and Registrations and Modifyng the IMSID Data Map Property

The following example runs DTLURDMO twice: first with a DM_COPY statement to copy data maps, and then with a REG_COPY statement to copy registrations and extraction maps. The REG_COPY statement also modifies the IMSID data map property.
The DM_COPY and REG_COPY statements also modify the schema name and IMSID data map property. In this example, the source system uses IM95 for the schema name for IMS data maps and IM95 for the RECON ID on registration groups and for the IMS system ID. The target system uses IM91 for the schema name for IMS data maps and IM91 for the RECON ID on registration groups and for the IMS system ID.
The first execution of DTLURDMO uses the following input statements: 
global statements

SOURCE systema;
TARGET systemb;

more global statements

DETAIL;
DM_COPY;
SELECT AM=DL1 SCHEMA=IM95;
MODIFY AM=DL1 IMSID=IM91;
RENAME SCHEMA=(IM95,IM91);
These statements achieve the following results:
  • The DM_COPY and SELECT statements copy IMS data maps with schema name IM95 and access method DL1 from the source system (PowerExchange Listener systema) to the target system (PowerExchange Listener systemb).
  • The RENAME SCHEMA statement changes the schema name from IM95 to IM91.
  • The MODIFY statement modifies the IMSID data map property for all selected data maps for which AM=DL1 from IM95 to IM91.
After DTLURDMO copies the data map from the source system to the target, a second exeuction of DTLURDMO copies the registration. This execution uses the following input statements: 
global statements

SOURCE systema;
TARGET systemb;

more global statements

DETAIL;
REG_COPY;
CREATEXMAPS LOC=TARGET;
SELECT DBID=IM95 DBTYPE=IMS;
MODIFY NEW_DBID=IM91;
RENAME IMSSCHEMA=(IM95,IM91);
These statements achieve the following results:
  • The REG_COPY and SELECT statements copy IMS registrations with DBID of IM95 from the source system (PowerExchange Listener systema) to the target system (PowerExchange Listener systemb).
  • CREATEXMAPS generates the new extraction map. This statement eliminate the need to run the utility with XM_COPY statement.
    LOC=TARGET specifies that the data map used to create the extraction map is loaded from the target destination.
  • The RENAME IMSSCHEMA statement changes the schema name from IM95 to IM91.
  • The MODIFY NEW_DBID statement changes the IMSID data map property to IM91.
When executing a REG_COPY statement, the DTLURDMO utility must load the IMS DBD if any of the following statements are also included:
  • CHECKXREF
  • RENAME DBD
  • RENAME IMSMAP
  • RENAME IMSSCHEMA
DTLURDMO retrieves the location of the IMS DBD library from the appropriate IMSID statement in the DBMOVER configuration file on the target system. The IMSID statement has the following syntax: 
IMSID=(
ims_ssid

      ,
dbdlib

     [,RECON=(
recon1
            
[,
recon2
]
            [,
recon3
])]
)
DTLURDMO uses the IMSID statement that has a value for IMS_SSID that matches one of the following values, listed in order of priority:
  1. If a MODIFY NEW_DBID statement is present, DTLURDMO uses this value, which represents the new data map property value.
  2. If no MODIFY NEW_DBID statement is present, DTLURDMO uses the IMSID data map property. This value can be different from the RECON ID value.
  3. If no MODIFY NEW_DBID statement is present, and the data map does not have a value for the IMSID property, DTLURDMO uses the value specified in the SELECT DBID= statement. This value is the value of the RECON ID of the registration group.
  4. If none of the previous conditions apply, DTLURDMO issues a message indicating that the registration cannot be copied and will be skipped.
0 COMMENTS
We’d like to hear from you!