2 Installing Oracle Connect and Oracle Studio

Hardware Requirements

The following table summarizes the hardware requirements for Oracle Connect.

Software Requirements

The following table summarizes the software requirements for Oracle Connect:

Hardware Requirements

The following table summarizes the hardware requirements for Oracle Connect.

Software Requirements

The following table summarizes the software requirements for Oracle Connect.

Transferring the Kit to the Dataset

You need to move the contents of the kit to the mainframe computer in the dataset that you allocated. When you copy the contents of the kit, you will see that the contents are now utilized.

Perform the following steps to copy the Oracle Connect installation kit contents to the mainframe:

1. Extract the compressed file to a folder on a computer running Microsoft Windows.

2. Open the Command console on the Windows computer.

3. Type FTP and the name of the mainframe computer where you want to connect. This creates an FTP connection to the mainframe machine. You may have to enter a user name and password to use the machine.

4. Type bin to transfer binary data.

5. Enter the following command to transfer the data from the .KIT file to the mainframe computer:

   put OCL10134.transmit.kit '[HLQ].transmit.kit' [replace]

   where:

   • OCL10134.transmit.kit is the name of your installation file.

   • (replace ensures that any data on the volume where the kit is installed is overwritten.

6. Enter the following command to tranfer the data from the .LOAD file to the mainframe computer:

   put OCL10134.transmit.load '[HLQ].transmit.load' [replace]

7. Close the FTP connection.

Copy and Install Programs into CICS

You must copy and install some supporting programs when you use a CICS session.

The following describes the steps necessary to copy and install these programs under CICS.

1. In the Data Set List Utility screen, type the name of the <HLQ> on the Dsname Level line. This will return a list of the files.

2. In the Command column next to the <HLQ>.LOAD, type M.

3. Type C next to following programs you are using. The available programs are listed below:

   • ATTHRDPL: Use this program when working under CICS. This is the CICS queue.

   • ATTCISD: Use this program when working under CICS.

   • ATTHRDPL: Use this program when working under CICS if you are using connection pooling.

   • ATTCALL: Use this program when working under CICS if you are using connection pooling.

   • ATTCNTRL: Use this program when working under CICS if you are using connection pooling.

   • TRANS3GL: Use this program if you are using the 3GL interface. This is an example program.

4. Exit the session, then start a new session.

5. Enter a new CICS session.

6. At the code line, run the following:

   CEDA INS PROG(<PROG NAME>) G(ATY)
   

   The <PROG NAME> is on one of the programs listed in step 3. Run this for each of the programs you are using.

Post-installation Procedures

Perform the following procedures after completing the installation to configure Oracle Connect.

• Allocate a dataset for INSTROOT.DEF.BRANDBIN, using 1 track and with RECFM=VB and LRECL=256. The block size is 6233.

  INSTROOT is the high-level qualifier where Oracle Connect is installed.

  Using FTP, copy the BRANDBIN file, in binary mode, from the Oracle Connect\DB2/DB Legacy Adapter directory to the mainframe, to INSTROOT.DEF.BRANDBIN.

• Define the LOADAUT library as an APF-authorized library

  Note:

  To define a DSN as APF-authorized, in the SDSF screen enter the command:

  "/setprog apf,add,dsn=INSTROOT.loadaut,volume=vol002"
  

  where vol002 is the volume where you installed Oracle Connect and INSTROOT is the high-level qualifier where Oracle Connect is installed.

  If the site uses SMS, then when defining APF-authorization in the SDSF screen, enter the following command:

  "/setprog apf,add,dsn=INSTROOT.loadaut,SMS"
  

  Ensure that the library is APF-authorized, even after an IPL (reboot) of the computer.

• Move the INSTROOT.USERLIB(ATTDAEMN) and INSTROOT.USERLIB(ATTSRVR) members to any active proclib, such as user.proclib, ATTDAEMN and ATTSRVR are run as started tasks.

  If you decide to change the name of the ATTSRVR member when you move it to a general high-level qualifier, then change the name specified in the StartupScript parameter in the daemon configuration to the new name:

  • Run INSTROOT.USERLIB(NAVCMD) and enter EDIT DAEMON IRPCDINI at the prompt.

  • Change the startupScript parameter from ATTSRVR to the new name for the server:

    <Workspace name="Navigator"
               startupScript="NEW_NAME"
               serverMode="reusable"
               ... />
    

  • Exit and save the change.

• Change the following line in the ATTDAEMN script to include the IP address and port of the z/OS platform.

  For example, before:

  // PARM='-B START IRPCDINI'
  

  After:

  // PARM='-B -L ip_address:2551 START IRPCDINI'
  

  Where ip_address specifies the IP address of the computer, 2551 is the default port for starting the daemon and IRPCDINI is the default daemon configuration.

• The ATTDAEMN and ATTSRVR started tasks need permission to use an Open Edition TCP/IP stack. The owner must be a user with OMVS segment defined and OMVS UID= 0000000000.

• In the security manager, such as RACF, define ATTDAEMN and ATTSRVR with a started task class and a general profile that enables the following:

  • Permission to issue master console commands.

  • START authority for the ATTSRVR job.

  • Access to an Open z/OS segment (that defines access to TCP/IP OA sockets).

  • ALTER authority on datasets under INSTROOT (to access to read, write, allocate and delete datasets under INSTROOT).

• The installation includes a PS, INSTROOT.DEF.GBLPARMS, that contains global environment information. This PS is read at startup and the correct software version is used, based on the details provided in the startup task.

  If you change the location of this member, you must also change the relevant cards in the following jobs to the new locations:

  • ATTSRVR: located in an active proclib, such as user.proclib

  • ATTDAEMN: located in an active proclib, such as user.proclib

  • NAVSQL: located in INSTROOT.USERLIB

• The input during the installation procedure is written to nnn.BUILDKIT.SRC(PARS). You can use this file to provide the same inputs if you rerun the installation, where nnn is the high-level qualifier you assign for the installation.

• For information about specifying Oracle Connect as the service using port 2551 in the TCP/IP network services file, consult TCP/IP documentation.

Starting the Daemon

Activate INSTROOT.USERLIB(ATTDAEMN) as a started task to invoke the daemon. For example, in the SDSF screen enter the following:

'/s ATTDAEMN'

Where INSTROOT is the high-level qualifier where Oracle Connect is installed.

To submit the daemon as a job, uncomment the first two lines of the ATTDAEMN JCL, change the PARM line as described earlier, and run the job using the subcommand. The ATTDAEMN JCL is similar to the following:

//*ATTDAEMN JOB 'RR','TTT',MSGLEVEL=(1,1),CLASS=A,
//* MSGCLASS=A,NOTIFY=&SYSUID,REGION=8M
//STEP1 EXEC PGM=IRPCD,
// PARM='-B  START IRPCDINI'
//* PARM='-B -L :8883 START'
//STEPLIB DD DSN=INSTROOT.LOADAUT,DISP=SHR
//SYSPRINT DD SYSOUT=A
//GBLPARMS DD DSN=INSTROOT.DEF.GBLPARMS,DISP=SHR
// EXEC PGM=IRPCD,COND=((1,EQ,STEP1),(2,EQ,STEP1)),
// PARM='-KATTDAEMN START ''INSTROOT.DEF.IRPCDINI'''
//STEPLIB DD DSN=INSTROOT.LOADAUT,DISP=SHR
//SYSPRINT DD SYSOUT=A
//GBLPARMS DD DSN=INSTROOT.DEF.GBLPARMS,DISP=SHR
//SYSDUMP DD DUMMY

Setting Up Oracle Connect for Reentrancy

All Oracle Connect load modules are reentrant to enable sub-tasking. Therefore, move INSTROOT.LOAD to the Link Pack Area (LPA).

Where INSTROOT is the high-level qualifier where Oracle Connect is installed.

Using the LPA reduces real storage usage (because everyone shares the LPA copy) and fetch time.

Setting up Oracle Connect to Access DB2CLI

In order to access DB2 CLI, you must have DB2 CLI installed on the machine. For details of DB2 CLI, refer to the IBM Call Level Interface Guide and Reference.

The Oracle Connect DB2 CLI driver uses an ODBCINI file. During installation of Oracle Connect, an ODBCINI file is defined as a member in NAVROOT.USERLIB.

The ODBCINI file is similar to the following:

; This is a comment line...; Example COMMON odbcini [COMMON]MVSDEFAULTSSID=DSN1; Example SUBSYSTEM odbcini for DSN1 subsystem [DSN1]MVSATTACHTYPE=CAFPLANNAME=DSNACLI

The PLANNAME value is the default DB2 Calling Level Interface (CLI) plan name. If a different plan is used, change the name to the correct plan.

You can specify other parameters in the ODBCINI file, as described in the IBM ODBC Guide and Reference.

You must bind to the plan specified in the PLANNAME parameter. The bind to the plan, check that the job DSNxxx.SDSNSAMP(DSNTIJCL) includes the following line:

BIND PLAN(DSNACLI)

Where DSNxxx is the DB2 high-level qualifier (the default is DSN610) and DSNACLI is the plan name specified for the PLANNAME parameter.

Oracle Connect and DB2 Security

All the libraries in the STEPLIB must be APF-authorized. Grant DB2 DISPLAY GROUP authorization to the ATTSRVR started task. Issue the following commands to the owner of the ATTSRVR started task:

GRANT TRACE(STAT)

GRANT TRACE(MON)

GRANT MONITOR2

The owner of the ATTSRVR strarted task must have privileges in DB2 to run offline.

Issue the following command:

-start trace(stat)

Preinstallation Tasks

Before starting the installation procedure, ensure that you have the following information is available:

• The root directory where you want to install Oracle Connect.

  Notes:

  The root directory cannot be a system root directory, /var or /tmp.

• The account name where Oracle Connect will run.

• Whether the installation source media is removable media or a disk archive file.

  If you are installing from the removable media that is not a default device in the system, you need to know the media device name (such as /dev/rmt/0m). See the operating system manuals or ask the system administrator to find out the device name for the site.

  If you are installing from the disk archive file, you need to know the name of the Oracle Connect disk archive file (such as /tmp/nav.2.0.tar).

• The shell being used: C-shell Korn,-shell, or Bourne-shell. The installation creates a startup file according to the indicated shell.

When running the installation below, use the following as the <filename>:

• For RedHat Linux: OCL10134-linuxrh.tar.Z

• For Linux Suse: OCL10134-linuxsuse.tar.Z

• For HP-UX: OCL10134-hpux.tar.Z

• For IBM AIX: OCL10134-ibmaix.tar.Z

• For Solaris Operating System (SPARC): OCL10134-sunsol2.8.tar.Z

Installing Oracle Connect

Perform the following steps to install Oracle Connect:

1. Transver the tar.Z file to th esystem.

2. Decompress the file using the following command:

   uncompress <filename>
   

3. Run the tar command, as shown in the following example:

   tar xvf <filename> nav_install
   

   The following message is displayed:

   x nav_install, nnnn bytes, mmmm tape blocks
   

Installation Tasks

Perform the following steps to install Oracle Connect:

1. Run the following command:

   ./nav_install
   

   This command initiates the installation procedure. The installation procedure is displayed in a series of screen prompts and responses.

2. Enter the full path of the disk archive (.tar) file, and press Enter.

3. Enter the root directory name for the installation, and press Enter. You must have a WRITE permission for this directory. The default directory is the users home directory.

   Notes:

   • The root directory cannot be a system root directory or /var or /tmp directory.

   • Oracle Connect is installed into a fixed directory named navroot.

4. Confirm the directory name in which Oracle Connect will be installed, and press Enter.

5. Enter the account name where you want Oracle Connect to run, and press Enter. This account name will be used for anonymous access to the server by clients. It can be changed after the installation is complete.

6. Confirm the account name, and press Enter.

7. Specify the required shell, under which Oracle Connect should run, and press Enter. The following options are displayed:

   • C-shell (/bin/csh).

   • Korn-shell (/bin/ksh)

   • Bourne-shell (/bin/sh)

8. Enter the account name for a user with administrative authorization. Optionally, press Enter to enable any user to administer Oracle Connect.

Post-Installation Tasks

After installing Oracle Connect, perform the following post-installation tasks:

• Configuring the Oracle Connect Environment

• Configuring the Oracle Connect Script

• Starting the Oracle Connect Daemon

Configuring the Oracle Connect Environment

When Oracle Connect is installed on a UNIX platform, using FTP, copy the brand.bin file to the Oracle Connect computer, to NAVROOT/bin.

Where NAVROOT is the directory where Oracle Connect is installed.

Configuring the Oracle Connect Script

The program that manages Oracle Connect server processes (nav_server) is accessed by a symbolic link to a file for the C-shell, Bourne and Korn shells.

To set up nav_server, perform the following steps:

1. In the bin directory, under the directory where Oracle Connect is installed, delete the existing link to nav_server using the following command:

   rm nav_server
   

2. In the bin directory, under the directory where Oracle Connect is installed, link to the required version of nav_server as follows:

   • C-shell: ln -s nav_server.csh nav_server

   • Bourne: ln -s nav_server.sh nav_server

   • Korn: ln -s nav_server.ksh nav_server

   Note:

   Instead of renaming files, use a symbolic link.

The Oracle Connect nav_login procedure defines the default environment when Oracle Connect runs. If you want site-dependent variables to be included in the environment, create a file called site_nav_login and save this file in the bin directory under the Oracle Connect root directory. nav_login runs site_nav_login automatically.

nav_login must be invoked to run Oracle Connect. It can be invoked from the user login script.

The command line for invoking nav_login varies according to the shell the user is running. The following table lists the different options for invoking the command line:

source root/bin/nav_login

. root/bin/nav_login.sh

. root/bin/nav_login.sh

In the nav_login command, root represents the root directory of the Oracle Connect installation. After running the login procedure, the environment variable NAVROOT points to this root directory.

Ensure that users have READ and EXECUTE permissions on the Server files. Use the chmod command to change the permissions.

Starting the Oracle Connect Daemon

The Oracle Connect daemon must run on a server for client/server access to Oracle Connect. To start the daemon with the system startup, add the following command invoking the daemon to the end of the /etc/inittab file:

nv:3:once:navroot/bin/irpcd -l ip:2551 start >/dev/console 2>&1

In this command, the symbol navroot should be replaced with the directory where Oracle Connect is installed and ip replaced by the ip address of the computer.

Installing Oracle Studio with the Wizard (SH installation)

You can install Oracle Studio by using the installation wizard. This allows you to easily carry out any standard or custom installation. Do the following for the Linux SH installation.

1. Install into a directory where you have permission.

2. Change the mode to execute mode. Type in:

   Chmod +x <file name>
   

3. Enter the following:

   ./ <file name>
   

   If you are not installing to the current directory, enter the full path.

Installing with a Silent Installation (RPM)

You can use the Linux RPM method to install Oracle Studio. Do the following to carry out a silent installation on Linux.

• Enter the following:

  rpm -i <file name>
  

  You can use RPM parameters to create a custom inslallation.