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

Required Authorities for Access to DB2 Resources

Required Authorities for Access to DB2 Resources

PowerExchange requires the following authority levels for access to DB2 for z/OS resources:
  • EXECUTE authority on the DB2 plan
  • SELECT authority on DB2 source tables
  • INSERT authority on DB2 target tables
  • LOAD authority on any DB2 target tables to be loaded by the DB2 LOAD utility
  • SELECT authority on the following DB2 catalog tables:
    • SYSIBM.SYSCHECKS
    • SYSIBM.SYSCHECKDEP
    • SYSIBM.SYSCOLUMNS
    • SYSIBM.SYSDATABASE
    • SYSIBM.SYSDATATYPES
    • SYSIBM.SYSDUMMY1
    • SYSIBM.SYSFOREIGNKEYS
    • SYSIBM.SYSINDEXES
    • SYSIBM.SYSKEYS
    • SYSIBM.SYSPACKAGE
    • SYSIBM.SYSPACKSTMT
    • SYSIBM.SYSPARMS
    • SYSIBM.SYSRELS
    • SYSIBM.SYSROUTINES
    • SYSIBM.SYSSEQUENCES
    • SYSIBM.SYSSEQUENCESDEP
    • SYSIBM.SYSSYNONYMS
    • SYSIBM.SYSTABLES
    • SYSIBM.SYSTABLESPACE
    • SYSIBM.SYSTRIGGERS
    PowerExchange requires SELECT authority on these tables to import metadata into the Designer or Developer tool when you create a mapping for a bulk data movement session.
Also, the user ID that DB2 uses to control PowerExchange user access to DB2 data in specific tables depends on the SECURITY and MVSDB2AF statement settings in the DBMOVER configuration member of the RUNLIB library.
The following table describes the user ID that is used under alternative statement settings:
MVSDB2AF Setting
SECURITY Setting
User ID for DB2 Access
CAF
0, 1, or 2
User ID under which the PowerExchange Listener is running
RRSAF
0 or 1
User ID under which the PowerExchange Listener is running
RRSAF
2
MVS user ID under which the user application is running

0 COMMENTS

We’d like to hear from you!