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

Running the DTLURDMO Utility on Linux, UNIX, and Windows

Running the DTLURDMO Utility on Linux, UNIX, and Windows

On Linux, UNIX, or Windows, run the utility by navigating to the Informatica PowerExchange directory and entering
dtlurdmo
on the command line as follows:
dtlurdmo
DTLURDMO_definition_file
For example:
dtlurdmo e:\powerexchange\bin\dtlurdmo.ini
The DTLURDMO definition file contains the DTLURDMO control statements. If no definition file is specified, PowerExchange looks for the
dtlurdmo.ini
file in the current path.
Source and target locations specified in the control statements can include z/OS and IBM i systems, provided that user IDs and passwords associated submitted with the control statements have the appropriate authority to access maps and registrations on those systems. Performance is similar to running the utility on the remote system since network overhead for the utility is low.
If you use the utility with the REGCOPY statement and do not include the FASTLOAD statement, utility performance can be slow. If you run the utility to copy registrations without the FASTLOAD statement, the system from which you launch the utility has no significant impact on performance. For information about the FASTLOAD statement, see REG_COPY FASTLOAD Statement.
To monitor progress of the utility in a command window, use the REPORT_DEST STDOUT statement.
If you run DTLURDMO on Linux, UNIX, or Windows to process maps or registrations on remote z/OS or IBM i systems, you can also monitor the progress in the DTLLOG of the remote PowerExchange Listener. Message
PWX-33304
indicates the start of a connection to the remote system, and messages
PWX-00408
and
PWX-00409
indicate the close of a result set.

0 COMMENTS

We’d like to hear from you!