Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. DTLDESCRIBE Metadata
  12. PowerExchange Globalization
  13. Using the PowerExchange ODBC Drivers
  14. PowerExchange Datatypes and Conversion Matrix
  15. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  16. Appendix B: PowerExchange Glossary

DMXCACHE_MAX_MEMORY_MB Statement

DMXCACHE_MAX_MEMORY_MB Statement

The DMXCACHE_MAX_MEMORY_MB statement enables PowerExchange data maps caching and configures the maximum size for the data maps cache in megabytes.
z/OS
DM_SUBTASK, DMXCACHE_DELETEECSA, and DMXCACHE_MULTIPLEJOBS
No
DMXCACHE_MAX_MEMORY_MB={
cache_size
|
0
}
For the
cache_size
variable, enter the maximum size for the data maps cache in megabytes. Valid values are from 0 through 4095. You must enter a value greater than 0 to enable data maps caching. If you accept the default value of 0, PowerExchange does not use data maps caching.
Default is 0.
  • Verify that the REGION size specified in the DTLLST step in the JCL is large enough to run the PowerExchange Listener job. For example, if you define DMXCACHE_MAX_MEMORY_MB=20, you might have to increase the REGION size by 20 MBs.
  • You cannot use data maps caching with IMS netport jobs.

0 COMMENTS

We’d like to hear from you!