Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Binding IBM DB2 for z/OS Packages Manually

Binding IBM DB2 for z/OS Packages Manually

If the IBM DB2 Bind Package job fails on the IBM DB2 for z/OS source, you can bind the packages manually on the source.
The following message appears if the IBM DB2 Bind Package job fails:
[informatica][DB2 JDBC Driver]Bind process is not active. Please ensure that the user has permissions to create packages. Packages cannot be created in an XA Connection.
To resolve the issue, perform the following steps:
  1. Go to the directory where you extracted the Data Archive installation files.
  2. Open the
    Optional
    folder.
  3. Extract the
    bind_files.zip
    file.
    The
    bind_files.zip
    file contains the
    CNTLFILE.XMIT
    and
    DBRMFILE.XMIT
    files.
  4. Log in to the source mainframe.
  5. Create the following datasets.
    • <userID>.CNTLFILE.XMIT
    • <userID>.DBRMFILE.XMIT
    For example, if your user ID is
    jane12
    , then use the following name for the datasets:
    • JANE12.CNTLFILE.XMIT
    • JANE12.DBRMFILE.XMIT
    Use uppercase for the name of the datasets.
  6. Enter the following properties for the datasets:
    DSORG=PS, RECFM=FB, LRECL=80, BLKSIZE=3120
  7. Access the source mainframe through FTP from the machine that contains the
    CNTLFILE.XMIT
    and
    DBRMFILE.XMIT
    files. Use the same user ID and password for the FTP as the one you used to log in to the source mainframe in step 4.
  8. Enter
    BIN
    to use the binary transfer mode.
  9. Enter the
    PUT
    command to transfer the
    CNTLFILE.XMIT
    and
    DBRMFILE.XMIT
    files to the source mainframe.
  10. Verify that the data from the
    CNTLFILE.XMIT
    and
    DBRMFILE.XMIT
    files transferred to the datasets you created in step 5.
  11. Log in to the source mainframe.
  12. From the ISPF option 6 or TSO Ready mode, enter the following
    RECEIVE
    command:
    RECEIVE INDS('userid.CNTLFILE.XMIT')
  13. At the prompt, enter
    DA('userid.DDJDBC.CNTL')
  14. Press
    ENTER
    .
    The system creates the partitioned data set
    DDJDBC.CNTL
    that contains the JCL and distribution packages.
  15. From ISPF option 6 or TSO Ready mode, enter the following
    RECEIVE
    command:
    RECEIVE INDS('userid.DBRMFILE.XMIT')
  16. At the prompt, enter
    DA('userid.DDJDBC.DBRMLIB')
  17. Press
    ENTER
    .
    The system creates the partitioned data set
    DDJDBC.DBRMLIB
    that contains the JCL and distribution packages.
  18. Edit the job
    userid.DDJDBC.CNTL(BIND)
    . Follow the instructions in the job to complete the following tasks:
    1. Bind the packages for the DataDirect Connect for JDBC DB2 driver.
    2. Grant the user the
      EXECUTE
      privilege.

0 COMMENTS

We’d like to hear from you!