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. EDMUOPTS - Service Aid Utility
  18. EDMXLUTL - Event Marker Utility
  19. HOSTENT - TCP/IP Address Reporter Utility
  20. PWXCATMY - MySQL Catalog Utility
  21. PWXUCCLPRT - Print Log Summary Utility
  22. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  23. PWXUCREG - Capture Registration Suspend Utility
  24. PWXUCRGP - Capture Registrations Print Utility
  25. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  26. PWXUGSK - SSL Reporting Utility for z/OS
  27. PWXUMAP - Map List Utility
  28. PWXUSSL - PowerExchange SSL Reporting Utility

Scope of Operands

Scope of Operands

Within the scope of a copy statement (DM_COPY, REG_COPY, or XM_COPY), DTLURDMO allows multiple occurrences of each of the following statements:
  • EXCLUDE
  • MODIFY
  • RENAME
  • SELECT
Multiple occurrences of these statements are supported to maintain backward compatibility and to provide flexibility when migrating a large number of objects. However, in most cases it is simpler and clearer to include multiple copy statements instead. This way, each copy statement is followed by at most one EXCLUDE, MODIFY, RENAME, and SELECT statement.
If you include multiple occurrences of the EXCLUDE MODIFY, RENAME, or SELECT statements, include a TESTMODE statement or a VALIDATE statement to run DTLURDMO in test mode and verify the operation of these statements. In addition, if you include multiple occurrences of the MODIFY or SELECT statements within the scope of a copy statement, PowerExchange issues a warning message to indicate that the outcome of these multiple statements might be unpredictable.

Behavior of EXCLUDE, MODIFY, RENAME, and SELECT Statements

The following rules summarize the behavior of the EXCLUDE, MODIFY, RENAME, and SELECT statements within the scope of a copy statement:
  • To determine which objects to exclude, DTLURDMO performs a logical OR operation on all the EXCLUDE statements.
  • To determine which objects to select, DTLURDMO performs a logical OR operation on all the SELECT statements.
  • The EXCLUDE and SELECT statements determine the scope of each RENAME statement. Each RENAME statement renames the specified objects that are selected by the SELECT statements and not excluded by the EXCLUDE statements.
  • The EXCLUDE and SELECT statements determine the scope of each MODIFY statement. The scope of each MODIFY statement is further restricted by the specified access method. Multiple MODIFY statements that specify different access methods are logically independent (OR operation).
  • If multiple MODIFY statements specify the same access method, DTLURDMO ignores all but the first statement.
  • Except in the case of multiple MODIFY statements that specify the same access method, the order of statements does not matter.

Example Using Multiple SELECT and MODIFY Statements

Suppose you need to copy several data maps that were defined with an access method of SEQ, and you need to modify the file name attribute in each data map.
The following statements might appear to be correct, but they do
not
produce the desired result:
DM_COPY; SELECT MAP=fbti SCHEMA=vsam ; MODIFY AM=KSDS FN=FPRSV.PAS.PSCODV1; SELECT MAP=scpd SCHEMA= flatfile ; MODIFY AM=SEQ FN=FPRS.PAS.D416.PSW.PLNXTR; SELECT MAP=sczp SCHEMA= flatfile ; MODIFY AM=SEQ FN=FPRS.PAS.D416.PSW.PLNSTAT;
In this example, the scope of the MODIFY statements is determined by all the SELECT statements within the scope of the DM_COPY statement, not just the immediately preceding SELECT statement. The following statement is disregarded, because it applies to the same access method and set of selected data maps (as determined by the SELECT statements) as a previous MODIFY statement within the scope of a single DM_COPY command:
MODIFY AM=SEQ FN=FPRS.PAS.D416.PSW.PLNSTAT
Instead, include multiple DM_COPY commands, with each DM_COPY command followed by a single SELECT command and a single MODIFY command:
DM_COPY; SELECT MAP=fbti SCHEMA=vsam ; MODIFY AM=KSDS FN=FPRSV.PAS.PSCODV1; DM_COPY; SELECT MAP=scpd SCHEMA= flatfile ; MODIFY AM=SEQ FN=FPRS.PAS.D416.PSW.PLNXTR; DM_COPY; SELECT MAP=sczp SCHEMA= flatfile ; MODIFY AM=SEQ FN=FPRS.PAS.D416.PSW.PLNSTAT;

0 COMMENTS

We’d like to hear from you!