Chapter 3: Installing the DB2 UDB Options

Installing DB2 UDB Options for CICS and IMS

Be sure you completed the tasks in Chapter 2, “Pre-Installation Tasks.”

Licensing information

The DB2 UDB Options for CICS and IMS requires a permanent authorization key. However, Sybase includes a temporary key, which is valid for 30 days, within the order at installation time. To avoid interrupting your operations, call Customer Service at 1-800-8Sybase (1-800-879-2273), select Option 3, then select Option 3 again, and request a permanent key.

When speaking with Customer Service, be sure to have this information ready:

Product name
Order number
For the machine you are using:
- Serial number
- Machine type
- Model number
A valid e-mail address

Please allow seven business days for the key to be generated and sent to you.

The following two procedures describe the installation steps necessary to install all Mainframe Connect options from the InstallShield wizard and to complete the installation for the DB2 UDB Options for both CICS and IMS. You should skip those installation steps that do not pertain to the option or options you have chosen to install.

The InstallShield wizard runs only on Windows.

To install from the InstallShield wizard

Start the InstallShield wizard from CD by executing setupwin.exe, which is in the root directory.

The initial dialog box displays the options available for installation. Click Next and Back to navigate through the wizard. To cancel the installation, click Cancel. Click Next to proceed.
Accept the terms of the user-license agreement by selecting your country in the drop-down list and selecting the option to indicate that you agree with the terms. Click Next.
Select the components you want to install and click Next.

If you are installing the Server Option for CICS API or the DB2 UDB Options for CICS and IMS, the Server Option for CICS runtime component will be automatically selected as you proceed to the next screen.
Provide the following JCL and system information:
- JCL Line 1-3 – valid jobcard that is used to run the final installation jobs in TSO.
- High Level Qualifier – used as a prefix for all data sets generated during installation.
- Volume – volume serial number that indicates where generated data sets are cataloged.
- Unit – unit parameter value that indicates the device requirements for cataloging generated data sets.
- Work Unit – for the use of temporary work data sets.
- Customer CICS, IMS, and MVS Loadlibs – pre-cataloged partitioned data sets (PDSs) or partitioned data sets extended (PDSE) into which configuration modules and sample programs are to be linked:
  - For CICS, this data set should be in the DFHRPL concatenation ahead of other Sybase libraries.
  - For IMS, this data set should be in the STEPLIB concatenation ahead of other Sybase libraries.
Click Next.
If you have chosen to install an option that uses CICS, DB2, or IMS, provide the following information where it applies. Otherwise, skip to the next step.
- CICS system datasets hlq – high-level qualifier for CICS system data sets is used to locate SDFHLOAD and other CICS libraries.
- RDO Dataset – name of the CICS RDO (DFHCSD) containing the application resource definitions used by your CICS region.
- RDO Group List – RDO group list used by your CICS region when executing an initial start.
- CICS Region Applid – VTAM APPLID for your CICS region.
- DB2 system datasets hlq – high-level qualifier used for DB2 system data sets.
- DB2 Exit Dataset – name of the DB2 exit data set used by your DB2 region.
- DB2 DSN Name – data set name (DSN) of your DB2 region.
- IMS datasets hlq – high-level qualifier for IMS system data sets, used to locate IMS libraries.
Click Next.
If you have chosen to install an API component, provide the following compiler information, which is used to configure JCL for compiling sample programs. Otherwise, skip to the next step.
- LE/370 datasets hlq – high-level qualifier used for the Language Environment 370, used here to locate data sets like CEELKED.
- COBOL Compiler Name – module used to execute COBOL in your environment.
- COBOL Compiler Loadlib – the system LOADLIB in which your COBOL compiler module resides.
- PLI Compiler Name – module used to execute PLI in your environment.
- PLI Compiler Loadlib – the system LOADLIB in which your PLI compiler module resides.
- C compiler datasets hlq – the C compiler data sets high-level qualifier used for C, used to locate data sets like SBCCMP.
- TCP/IP datasets hlq – the TCP/IP data sets high-level qualifier used to locate data sets like SEZATCP.
Click Next.
If you have chosen to install the Client Option for CICS, provide the following information for configuring a host connection definition for the Client Option. Otherwise, skip to the next step.
- TCP Address Space Name – name of your TCP/IP region.
- Server Name – name by which your Client Option applications refers to the remote server.
- Server TCP Host Name – DSN name for the remote server.
- Server TCP Host Port – TCP/IP port used by the remote server.
Click Next.
(For CICS only) If you have chosen to install the Server Option for CICS or the DB2 UDB Option for CICS, provide the following information for configuring a TCP/IP listener for these options. Otherwise, skip to the next step.
- TCP Address Space Name – name of your TCP/IP region.
- Listener Port – port on which the option listens.
The Server Option for CICS and the DB2 UDB Options for CICS share the same TCP/IP listener.
Click Next until the wizard displays the information you entered in steps 5 through 8. Review this information and, if necessary, click Back to return to previous screens and make corrections.
Click Next until the wizard displays a dialog box for FTP information. Provide the following data for establishing an FTP session to your mainframe:
- Userid – mainframe user ID for the FTP session.
- Password – password for the FTP session.
- Mainframe Host Name – mainframe DSN name.
- FTP Port – control port used by your mainframe FTP server, usually 21.
- VOL/UNIT Assignment – specify either a volume serial number and unit assignment for FTP, or allow FTP to use default values.
  
  If you specify a volume serial number that does not exist, FTP suspends operations until the mainframe responds to a message requesting that the volume be mounted.
- Log FTP Commands – indicates where FTP log information is to be written. This log information may be useful in troubleshooting FTP problems.
When you click Next, the installer wizard will create JCL and upload the selected components to your mainframe.
Close the installer wizard.

To complete the installation of your Mainframe Connect components, review and submit JCL from TSO. If you are installing multiple components, Sybase strongly suggests you install in the following sequence:

Client Options for CICS, and IMS and MVS
Server Options for CICS, and IMS and MVS
DB2 UDB Options for CICS and IMS
Any other options

To complete the installation

Locate the installation JCL for the DB2 UDB Options:

For CICS, in hlq.AMD2150.CICSDB2.JCL
For IMS, in hlq.AMD2150.IMSDB2.JCL

where hlq is the high-level qualifier you specified in step 5.

Run the following jobs in the order they are described here, where x is an integer that denotes the order in which the job is to be run in the overall sequence of jobs.

Ignore jobs that are not present or relevant to the option you are installing.

IxRECV – runs IKJEFT01 to use the TSO RECEIVE command to build and populate the product libraries.

IxPSB – (for IMS only) creates the IMS PSBs.

Add these transactions to the IMS Gen. Their definitions are included in the hlq.AMD2150.IMSDB2.CTRL(AMD2IMS) data set.

APPLCTN  PSB=SYRTIMS,PGMTYPE=TP,SCHDTYP=PARALLEL
TRANSACT CODE=SYRT,PRTY=(7,10,2),INQUIRY=(NO,RECOVER),              X
        MODE=MULT,EDIT=(ULC,),MSGTYPE=(MULTSEG,RESPONSE,1)


APPLCTN  PSB=SYBTEXT,PGMTYPE=TP,SCHDTYP=PARALLEL
TRANSACT CODE=SYTX,PRTY=(7,10,2),INQUIRY=(YES,NORECOV),             X
        MODE=MULT,EDIT=(ULC,),MSGTYPE=(MULTSEG,RESPONSE,1)

APPLCTN  PSB=SYCAIPGM,PGMTYPE=TP,SCHDTYP=PARALLEL
TRANSACT CODE=SYSP,PRTY=(7,10,2),INQUIRY=(YES,NORECOV),                        X
             MODE=MULT,EDIT=(ULC,),MSGTYPE=(MULTSEG,RESPONSE,1)

IxRDO – (for CICS only) runs the CICS Resource Definition Utility, DFHCSDUP, to define the transaction, program, and file entries for the DB2 UDB Option for CICS. If your CICS region has had a previous version of the DB2 UDB Option, you may need to uncomment or change the DELETE and REMOVE entries at the top of the RDO input.
IxVSAM – (for CICS only) allocates the VSAM data sets used for error and trace logging.
IxRPC – (for CICS only) adds definitions to the SYRPCFIL dataset, which is created during the installation of the Server Option and required for the DB2 UDB Option. If DB2 is not to be used in this CICS region, run the IxRPC1 job instead.
IxBIND – binds the DB2 plans required for the DB2 UDB Option.
- The asterisk and period (*.) before AMD2PKG.* in the PKLIST parameter of the BINDPLAN job may not be required on your DB2 system.
- In the Server Option for CICS and IMS configuration module SYGWXCPH, a parameter called CHARSETSRV can be set to “iso_1” or “utf8”. The DB2 UDB Options for CICS and IMS work with the CHARSETSRV parameter. This parameter determines which of two DB2 packages, AMD2DB2 or AMD2DBA, are used. If the value of CHARSETSRV is “iso_1,” the DB2 packages must be bound with ENCODING(EBCDIC), which is the default. If the value of CHARSETSRV is “utf8,” the DB2 packages must be bound with ENCODING(1208).
IxDELETE – (optional) deletes the data sets in the TSO XMIT format used for the installation.

Run the following jobs if you want to compile and link-edit the sample applications provided with the DB2 UDB Options for CICS and IMS:

PAMDCAMX – assembles and links the message module for the DB2 UDB Options.
PAMDPXIT – compiles and links the parser exit module.
PASMEXIT – assembles and links various exits for the DB2 UDB Options.

If you are migrating from a previous version of the DB2 UDB Options for CICS and IMS, use the TRSDROP member in the CTRL library as input to SPUFI to drop the old catalog stored procedure (CSP) tables and views.

Create tables and views for the CSPs as input to SPUFI using member TRSCREAT or TRSCREA2 in the CTRL library. These points will help you decide which member to use:

TRSCREAT verifies whether the current user has some privilege on a requested object using the current sqlid. If the current sqlid does not have permissions on an object, granted either explicitly or to PUBLIC, then the CSPs do not return information for that object.
TRSCREA2 enables faster CSP processing because it does not verify that the current user has a privilege on a requested object.

These conditions apply when using TRSCREA2:
- Anyone who can execute the CSP can obtain information about all DB2 objects, even if that user does not have privileges on those objects.
- The accessible_table column in sp_server_info is ineffective.

Edit and run the TRSGRANT member of CTRL using SPUFI to grant authorization for users to run the CSPs.

Create a collection ID by issuing the following SQL command to DB2 UDB (using a utility like TSO batch or SPUFI):

GRANT PACKADM ON COLLECTION AMD2PKG TO userid

For each additional DB2 subsystem to be accessed by the DB2 UDB Options for CICS and IMS, repeat steps 2 (IxBIND), 4, 5, 6, and 7.

Follow these specific instructions for either CICS or IMS:

For CICS only:

Edit the CICS start-up procedure to include the DB2 UDB Option for CICS LOADLIB library in the DFHRPL concatenation. This library should be placed before the load library for the Server Option for CICS.

(This step is optional.) Alter the message table using the AMD2CAMX member of SOURCE as a prototype. Assemble and link the message table using the AMD2CAMX member of JCL. For details on changing the message table, see Chapter 5, “Customizing the DB2 UDB Option for CICS Messages.”

Recycle your CICS region.

For each additional CICS region in which the DB2 UDB Option will be installed, repeat step 2 (IxRDO, IxVSAM, IxRPC) and step 9, making adjustments to the JCL where appropriate.

For IMS only:

Cycle the IMS region.

Edit the addcat15-0ims script (delivered with the DirectConnect for z/OS Option), replacing “region” with the name of your IMS region. Run isql to the DirectConnect for z/OS Option TRS with this script as input to add the RPCs to the DirectConnect for z/OS Option TRS.

For each additional IMS region for which DB2 UDB Option will be installed, repeat step 2 (IxPSB) and step 9.