Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Configuring IMS ODBA Access to IMS Data

Configuring IMS ODBA Access to IMS Data

To use IMS ODBA to access IMS data, you must complete some PowerExchange and IMS configuration tasks on the z/OS system.
PowerExchange uses IMS ODBA access when the IMS data map specifies
IMS ODBA
as the access method or when you override the
DL/1 BATCH
access method to
IMS ODBA
for a database row test or PowerCenter bulk data movement session.
IMS ODBA queries run as PowerExchange Listener subtasks and use the Listener port.
To use ODBA access, perform the following configuration tasks:
  • APF-authorize the PowerExchange Listener STEPLIB libraries.
  • Include the RESLIB library in the STEPLIB library for the PowerExchange Listener for ODBA access, or verify that the RESLIB is accessible through the LNKLST concatenation on the z/OS system.
  • Verify that each PSB contains defined PCBNAMEs.
  • Create an IMS data map that specifies
    IMS ODBA
    as the access method, or override the
    DL/1 BATCH
    access method in an IMS data map with IMS ODBA. You can override the access method in the PowerCenter session properties or when configuring a database row test.
    You can also override the IMS SSID, PSB name, and PCB name for a PowerCenter session or database row test.
  • In the DBMOVER configuration member in the RUNLIB, add the IMSID=
    ssid
    and ODBASUPP=YES statements. Then restart the PowerExchange Listener for these DBMOVER changes to take effect.
  • Verify that the IMS Resource Recovery Services (RRS) is active on the system. In the DFSPB
    xxx
    member of the IMS PROCLIB, specify RRS=Y.
  • Assemble and linkedit the IMS load module for configuring ODBA access to data. Use JCL that is similar to the following JCL:
    //ULIA JOB (),CLASS=A,MSGCLASS=H,MSGLEVEL=(1,1),REGION=4M //* //STEP1 EXEC HLASMCL, // PARM.C=('RENT') //C.SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB // DD DISP=SHR,DSN=IMS710.ADFSMAC //C.SYSIN DD * DFSIMS70 CSECT * * THE DFSPRP MACRO GENERATES THE DRA STARTUP TABLE * THERE ARE A FEW MORE POSSIBLE PARMS DFSPRP DSECT=NO, GENERATE X FUNCLV=1, FUNCTION LEVEL X DDNAME=CCTLDD, DDNAME FOR DRA RESLIB X DSNAME=IMS1210.SDFSRESL, DSNAME FOR DRA RESLIB X DBCTLID=
    IMSC
    , DBCTL IDENTIFIER X USERID=, USERID X MINTHRD=2, MIN NUMBER OF THREADS X MAXTHRD=7, MAX NUMBER OF THREADS X TIMER=60, IDENTIFY TIMER VALUE DEFAULT X FPBUF=5, NUMBER OF FP BUFFERS PER THREAD X FPBOF=5, NUMBER OF FP OVERFLOW BUFFERS X SOD=A, SNAP DATASET OUTPUT CLASS X AGN=, APPLICATION GROUP NAME X TIMEOUT=60, DRATERM TIMEOUT VALUE X IDRETRY=0, IDENTIFY RETRY COUNT X CNBA=10 TOTAL FP NBA BUFFERS FOR CCTL END //L.SYSLMOD DD DSN=ABC.A.LOAD(DFS
    IMSC
    0), // DISP=SHR
    The L.SYSLMOD DD statement must specify a module name that has in the following format: "DFS" +
    DBCTLID_value
    + "0". This module name must match the SSID for the control region and must be specified in the IMS data map. In this example JCL, the module name is DFSIMSC0.

0 COMMENTS

We’d like to hear from you!