Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Edit the DBMOVER Configuration Member on the z/OS System

Edit the DBMOVER Configuration Member on the z/OS System

Edit the DBMOVER configuration member.
Verify that the member includes a LISTENER statement. The LISTENER statement defines the TCP/IP port on which a named PowerExchange Listener process listens for work requests. The default DBMOVER member includes the required LISTENER statement.
In addition to the LISTENER statement, you can include the following statements in the DBMOVER configuration member to minimize data map I/O:
DMXCACHE_MAX_MEMORY_MB=20 DM_SUBTASK=R
When Data Archive accesses PowerExchange data maps through the PowerExchange Listener, every data map in the DATAMAPS KSDS is opened and processed. The DMXCACHE_MAX_MEMORY_MB and DM_SUBTASK statements configure the PowerExchange Listener on z/OS to use data maps caching and a data maps subtask in read-only mode.
To further reduce data map
I/O
, limit the number of data maps in the DATAMAPS file. For best results, limit the number of data maps to 100.
For more information about the DBMOVER configuration member, see the
PowerExchange Reference Manual
.