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. How to Create Business Rules to Archive and Purge Transactional Data
  9. How to Uninstall Data Archive 5.1
  10. How to Uninstall Data Archive 5.3
  11. How to Use Scripts to Change Database User Passwords in the ILM Repository
  12. IBM DB2 Database Connectivity and Setup for Data Archive
  13. Installing Data Visualization
  14. Integrating Third-Party Schedulers in ILM Engine
  15. Parallel Processing in Data Archive
  16. Seamless Access Configuration for Siebel Applications
  17. Seamless Access Setup for Oracle E-Business Suite
  18. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  19. Using Multiple Engines in an ILM Environment
  20. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  21. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Configure the PowerExchange Listener JCL on z/OS

Configure the PowerExchange Listener JCL on z/OS

Configure the PowerExchange Listener JCL before starting the PowerExchange Listener the first time. PowerExchange provides PowerExchange Listener JCL in the following members of the RUNLIB library:
  • PWXLSTNR runs PowerExchange as a started task.
  • STARTLST runs PowerExchange as a batch job.
When you ran the XIZZZ998 job during installation, the PWXLSTNR member was copied to the PROCLIB library.
  1. Verify that the STEPLIB DD concatenation in the PowerExchange Listener JCL includes the load libraries for your source DBMSs.
    Usually, the PowerExchange LOADLIB library occurs before the data-source load libraries in the concatenation.
    The STEPLIB concatenation in the STARTLST member includes the load libraries for all data sources in a proper order.
  2. Verify that the PARM statement specifies the node name that is defined in the LISTENER statement of the DBMOVER configuration file.
  3. In the REGION parameter of the EXEC statement, enter a region size. The region size indicates the amount of storage to allocate for running the PowerExchange Listener.
    The sample JCL specifies a region size of 128 MB in the EXEC statement.
    Informatica recommends a region size of 0M, which indicates no storage limit.
    If you omit the REGION parameter, the system default applies.
  4. Verify that the TIME parameter in the EXEC statement is set to NOLIMIT. The NOLIMIT setting enables the PowerExchange Listener job to run without a time limit and prevents timeout-related abends that might occur with abend code S322.
  5. If the SECURITY statement in the DBMOVER configuration file is set to 1 or 2, APF-authorize the PowerExchange LOADLIB library and any other load libraries in the STEPLIB DD concatenation of the PowerExchange Listener JCL.
For more information, see the
PowerExchange Bulk Data Movement Guide
.