Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

APF-Authorizing Copies of IDMS Load Libraries

APF-Authorizing Copies of IDMS Load Libraries

To meet the PowerExchange APF-authorization requirement, you can APF-authorize the copies of the system IDMS load libraries that are optionally created during PowerExchange installation.
If you apply maintenance or schema changes to the system IDMS load libraries, you must also apply these changes to the copies of the load libraries or re-create the copies by rerunning the XIDIDM10 job. Otherwise, the bulk data movement might not preserve data integrity.
If you do not want to maintain and APF-authorize copies of the IDMS load libraries, you can use the MVS Program Call services routine that PowerExchange provides to meet the APF authorization requirement.
To APF-authorize copies of IDMS load libraries:
  1. During PowerExchange installation, add the following statement to the SETUPIDM JCL before you run the job:
    //STEP1 EXEC SUBMJOB,MEMBER=XIDIDM10
    The XIDIDM10 job creates copies of the IDMS load libraries under the default names of
    hlq.
    IDMS.LOADLIB and
    hlq
    .IDMS.DBA.LOADLIB.
  2. APF-authorize the IDMS load library copies that were created by the XIDIDM10 job at PowerExchange installation.
  3. Verify that the STEPLIB DD in the PowerExchange Listener JCL includes the
    hlq.
    IDMS.LOADLIB and the
    hlq
    .IDMS.DBA.LOADLIB libraries.
    If you run the PowerExchange Listener as a batch job, the JCL is in the STARTLST member of the RUNLIB library. If you run the PowerExchange Listener as a started task, the JCL is in the PWXLSTNR member of the PROCLIB library.
  4. Verify that all other libraries in the STEPLIB DD statement of the PowerExchange Listener JCL are APF‑authorized. Lack of APF-authorization for some of these libraries negates PowerExchange authorization to access IDMS data through the PowerExchange Listener and will cause the PowerExchange Listener to not start.

0 COMMENTS

We’d like to hear from you!