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

Control Statement Overview for the DTLURDMO Utility

Control Statement Overview for the DTLURDMO Utility

DTLURDMO control statements are of the following types:
  • Global statements control overall program execution or provide basic information, such as user name or password. Global statements remain active for the entire DTLURDMO execution. You can include them only once in the input file or stream. The REPORTDEST global statement should be entered at the beginning of the statement set. You can include multiple REPORTDEST statements in the input file or stream. The remaining statements can be included only once in the input.
  • Copy statements specify the type of copy to perform:
    • DM_COPY copies data maps.
    • REG_COPY copies capture registrations and, optionally, extraction maps.
    • XM_COPY copies extraction maps.
      Copy statements have no operands but can be followed by optional statements. Only a single type of copy statement can appear in the input file or stream, but it can appear multiple times.
  • Optional statements follow a copy statement and are valid only for the scope of the execution of the copy statement. Optional statements become inactive when PowerExchange encounters a subsequent copy statement. Optional statements filter the objects selected, rename objects, change object attributes, and set optional functions for the copy.

0 COMMENTS

We’d like to hear from you!