Installation Worksheet for the Extender for Db2

The following is an overview of the steps that are performed to install the Extender for Db2, with variations based on specific user and system requirements. The worksheet that follows the overview will help you determine which steps are required for your installation.

Overview

1. Unload two data sets from the tape.
2. Copy Extender Entry points.
3. Link-edit the Extender for DB2 module with your DB2 entry points (optional).
4. Set up the parameter file EDAPARMS (optional).
5. Link the Extender for DB2 interceptors with your application program (optional).
6. Prepare run-time allocation streams.

Note: For more information on the software and hardware requirements that must be met before proceeding with installation, see Installation Requirements.

Worksheet

Answer the questions on the following Worksheet, which is intended to help you to differentiate between installation types based on specific user and system requirements. Proceed as instructed, following the detailed information in the referenced steps, as appropriate for your installation.

The Extender for Db2 is shipped as part of the z/OS PDS Deployment Server.

Are you planning to install the PDS Deployment Server in the same z/OS LPAR as the Extender for Db2?

• If Yes:
  • Install the server first, then skip Step 1. Unload Two Data Sets From the Tape and proceed to Step 2. Copy Extender Entry Points. (Not that Step 1 is not necessary because qualif.HOME.LOAD and qualif.HOME.DATA are unloaded during the PDS Deployment installation.)
  • Use the PDS Deployment EDAENV dataset, located at qualif.PDS.server_type.DATA (rather than the simplified one provided in the sample job streams included in this document).
• If No, run Step 1. Unload Two Data Sets From the Tape, followed by Step 2. Copy Extender Entry Points.

Will Db2 Extender talk directly to the local Db2 subsystem (without using a server)?

• If Yes, run Step 3. Link-edit the Extender for DB2 Module With DB2 Entry Points (Optional).
• If No, skip Step 3.

Are you installing Db2 Extender without a local Db2 subsystem?

• If Yes, run Step 4. Configure the Parameter File EDAPARMS (Optional) to define a default server name.
• If No, Step 4 is optional.

Does your application require explicit link-edit to IBM's Db2 interface modules (DSNALI, DSNELI or DSNTIAR) or does it explicitly load the interface modules?

• If explicit link-edit, run Step 5. Link the Extender for DB2 Interceptors With Your Application (Optional).
• If explicit load, skip Step 5.

In which mode does your application run?

Interactive: Are you running QMF?

• If Yes, prepare your run-time CLIST from the sample provided in Step 6.1. Call Attach Facility (CAF) With Explicit Load of DSNALI.
• If No, are you running Call Attach Facility (DSNALI) or DSN Command Processor (DSNELI)?
  • If DSNALI, prepare your run-time CLIST by converting the sample JCL in Step 6.2. Call Attach Facility (CAF) With Link-Edit of DSNALI into a CLIST.
  • If DSNELI, prepare your run-time CLIST by converting the sample JCL in Step 6.3. DSN Command Processor (TSO Attach) into a CLIST.

BATCH: Are you running QMF?

• If Yes, prepare your run-time JCL from the sample provided in Step 6.1. Call Attach Facility (CAF) With Explicit Load of DSNALI.
• If No, are you running Call Attach Facility (DSNALI) or DSN Command Processor (DSNELI)?
  • If DSNALI, prepare your run-time JCL from the sample provided in Step 6.2. Call Attach Facility (CAF) With Link-Edit of DSNALI.
  • If DSNELI, prepare your run-time JCL from the sample provided in Step 6.3. DSN Command Processor (TSO Attach).