4 Installation

4.1.1 Installation Checklist

• Step 1:  Perform Preinstallation Tasks

• Step 2:  Install the Oracle Transparent Gateway for DB2 Software

4.1.2 Post-installation Checklist       

• Step 1: Download and Install Patches

• Step 2: Add Program Properties

• Step 3: Authorize the Gateway Load Library

• Step 4: Re-IPL z/OS or Use Dynamic z/OS Commands

4.2.1 Step 1:  Perform Preinstallation Tasks

Oracle Transparent Gateway for DB2 is part of the Oracle Database for z/OS distribution. Before you can install the software, you need to perform various preinstallation tasks. For preinstallation instructions, refer to the Oracle Database Installation Guide for IBM z/OS (OS/390). After you have performed the required preinstallation tasks, you will be referred back to this manual to perform installation tasks specific to the Oracle Transparent Gateway for DB2. At that point, continue with the following steps.

4.2.2 Step 2:  Install the Oracle Transparent Gateway for DB2 Software

The following sections describe how to install the Transparent Gateway for DB2 10g for z/OS Software:

• Review Product-Specific Installation Guidelines

• Run the Installer and Install the Software

• Run the Generated Installation Job

Review Product-Specific Installation Guidelines

Review the following guidelines before starting the Installer:

• Using the Oracle Universal Installer

  Use the installer from the current release only to install components from this release. An installer from an earlier release will not install the necessary components.

• Reinstalling the Gateway Software

  If you reinstall gateway software into an Oracle home directory where a gateway is already installed, you must also re-install any components that were installed before you began the re-installation.

Run the Installer and Install the Software

Run the Installer and install the software, as follows:

1. Log in as the Oracle software owner user (the user performing the installation) and set the DISPLAY environment variable, if necessary.

2. To start the Installer, enter the following commands, where directory_path is the path of the Disk1 directory on the hard disk:

   $ /directory_path/runInstaller
   
   

   If the Installer does not appear, refer to the Troubleshooting appendix of the Oracle Database Installation Guide for IBM z/OS (OS/390) for information on troubleshooting.

3. Use the following guidelines to complete the installation:

   • Follow the instructions displayed in the Installer windows. If you need additional information, click Help.

   • When the Installer prompts you to run a script with root privileges, enter a command similar to the following in a terminal where you are logged in as the root user, then click Continue or OK:

     $ /oracle/v10g/root.sh
     
     

   • If you encounter errors while installing or linking the software, refer to the Troubleshooting appendix of the Oracle Database Installation Guide for IBM z/OS (OS/390) z/OS for information on troubleshooting.

4. On the Select a Product to Install panel, there are two options. Select the option Oracle Transparent Gateway for DB2 10.2.0.2.0, to install the gateway software. You must install the software before configuring it.

   You can configure the gateway within the same Installer session or at a later time by running the Installer again and choosing the ConfigureOracle Transparent Gateway for DB2 10.2.0.2.0 option.

Run the Generated Installation Job

1. Run the CPLNKLST job in the INSTLIB library of the installation High Level Qualifier (HLQ) to move the load modules from AUTHLOAD to the linklist library. Note that if you choose different HLQs for the installation and configuration steps two INSTLIBs will be generated. This is the only step referring to installation-HLQ INSTLIB. For the rest of the book, INSTLIB refers to the configuration-HLQ INSTLIB.

2. Refresh the linklist by issuing the following command to a z/OS console:

   F LLA,REFRESH
   

4.3.1 Step 1: Download and Install Patches

Check the OracleMetalink Web site for required patches for your installation. To download the required patches, perform the following steps:

1. Using a Web browser, go to the following Web site:

   http://metalink.oracle.com
   
   

2. Log in to OracleMetalink. If you are not an OracleMetalink registered user, then click Register for Metalink! and follow the registration instructions.

3. On the main OracleMetalink page, click Patches.

4. Use the Simple Search feature to search for Product or Family. Then, specify the following information:

   • In the Product or Family field, specify the option for the Oracle Transparent Gateway for DB2.

   • In the Release field, specify the current release number.

   • In the Patch Type field, specify Patchset/Minipack.

   When you have filled in the required information, click Go.

4.3.2 Step 2: Add Program Properties

The gateway and network service region programs must run nonswappable and noncancelable, and should not be subject to system time limits.  In addition, the gateway service runs in protect key 7.  These attributes are indicated by adding entries for these programs to the z/OS Program Properties Table (PPT), through a member of the SYS1.PARMLIB data set named SCHEDxx, where xx is a 2-letter or 2-digit suffix.  You may need to work with your systems programmer to determine the correct member name and to add the entries.  The entries that you add should be similar to those in the following example.  The comments, which are included for clarity, are allowed but are not required.

/* SCHEDxx PPT entry for Oracle gateway region */
PPT PGMNAME(ORARASC)    /* Program (module) name  */
  NOCANCEL              /* Not cancelable         */
  KEY(7)                /* Protection key         */
  NOSWAP                /* Not Swappable          */
  SYST                  /* Not subject to timing  */
  /* SCHEDxx PPT entry for Oracle network region  */
PPT PGMNAME(ORANET)     /* Program (module) name  */
  NOCANCEL              /* Not cancelable         */
  NOSWAP                /* Not swapable           */
  SYST                  /* Not subject to timing  */

The entries in the SCHEDxx member are normally read at z/OS IPL.  You can cause z/OS to re-read the member without an IPL by using the SET SCH operator command.  The PPT entries must take effect before Oracle gateway and network services are started.

For details about the SCHEDxx member, the PPT, and the SET SCH command, refer to the IBM manuals MVS Initialization and Tuning Reference and MVS Systems Commands.

4.3.3 Step 3: Authorize the Gateway Load Library

You must APF-authorize the gateway AUTHLOAD library. 

To perform this step, first select your gateway data set name qualifiers.  If an Oracle Database 10g server is currently installed, then these qualifiers must be different from the qualifiers used for the Oracle Enterprise for OS/390 server.  The disk volume for the gateway AUTHLOAD library is also specified in this step. 

Because future installation procedures for updates or service might require Oracle modules to reside in their own authorized library, Oracle Corporation does not recommend installing the authorized Oracle load modules in an existing authorized library.

To mark the gateway load library as authorized, use ISPF EDIT, the IEBUPDTE utility, or an equivalent function to add the gateway load library name to the appropriate PROGxx or IEAAPFxx member in SYS1.PARMLIB (where xx is the value in the APF=xx parameter specified in IEASYSnn or by the system operator when the z/OS system is IPLed). 

You can also authorize the load library in the JCL for the gateway as you proceed through the installation.  For example:

// SETPROG APF,ADD,DSN=name_of_your_load_library,VOL=VOLSER

This is generally the simplest method of APF authorizing a library. For SMS-managed libraries, specify SMS instead of VOL=VOLSER.

4.3.4 Step 4: Re-IPL z/OS or Use Dynamic z/OS Commands

The Oracle AUTHLOAD library can be APF-authorized dynamically by using the SETPROG system command.  You can use these commands to avoid an IPL.  However, you still need to make the changes to the SYS1.PARMLIB members as discussed in "Step 3: Authorize the Gateway Load Library".  These changes to the SYS1.PARMLIB members are necessary for APF entries to be permanent.

You must IPL z/OS or use the SETPROG system commands to ensure the Oracle AUTHLOAD library is APF-authorized before you bring up a gateway.