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

EVENT Command Usage

EVENT Command Usage

To use this command, include it as a control statement in a batch job. Then, run the job to create the event marker. The following rules apply to specifying this control statement:
  • Your statement should be contained within columns 1 through 71.
  • If your statement will not fit in this range, you must have a character in column 72 to indicate that your statement continues on more than one line.
  • A statement that continues on more than one line must contain only a single command.
  • Continued statements must begin in column 1, if column 71 on the previous line is blank.
  • A statement can use up to a 38 lines.
  • You can use a maximum of 255 blanks to separate commands and keywords.
The following additional information is listed for this command:
  • Before you run a job to create an event marker, be sure that the PowerExchange Logger is active.
  • A PowerExchange Logger failure could cause the logger to stop while running an event marker job. In this case, the control statements processed prior to the failure are still accepted. Conversely, the control statement that is in progress when the PowerExchange Logger fails, and the subsequent control statements, cause the event marker utility to abend.
  • Take care if running this command while the PowerExchange active log is receiving other log records for the source object that the marker affects. This can mix the event marker in with the other records, producing unexpected results.
  • When the utility successfully records the event marker record in the PowerExchange log, the utility displays message DTLEDM175016I. This message provides the RBA of the event marker record within the log. You may need the RBA to reference that record.
  • This utility obtains the name of the PowerExchange Logger that it accesses from the default options module,
    EDMSDIR
    .

0 COMMENTS

We’d like to hear from you!