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

Cache Operation

Cache Operation

If you configure the control file to find RID fields, the utility connects to the PowerExchange Listener on the z/OS system and reads data records. The utility saves downloaded data records to a temporary disk cache to process them. The utility deletes the cache files when it finishes execution or after it generates each data map, depending on the value of the flushDataMode element that you specify in the control file.
The default read record limit is 10,000 records. The utility stores up to this number of records in memory. Any records above this limit are spilled to disk. for example, if the control file specifies readRecordLimit=15,000, 10,000 records are cached in memory and 5,000 records are spilled to disk.
The maximum record length that PowerExchange supports is 144 KB. This record length correlates to approximately 1.37GB of RAM (10000*144*1024 bytes). Ensure that the infacmd JVM is configured to run with a suitably large heap size. A setting of -Xmx1500m is usually sufficient.
To configure cache operation, define the cacheConfig element in the control file. The cacheConfig element includes the following elements:
  • cachePath
  • flushDataMode
For more information about cacheConfig, see CacheConfig Complex Type.

0 COMMENTS

We’d like to hear from you!