Skip Headers
Oracle® Connect for IMS, VSAM, and Adabas Gateways Installation and Configuration Guide
11g Release 1 (11.1) for IBM z/OS

B32527-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Installing Oracle Connect for IMS, VSAM, and Adabas Gateways

This chapter guides you through the installation procedure of Oracle Connect for IMS, VSAM, and Adabas Gateways.

To install Oracle Connect for IMS, VSAM, and Adabas Gateways, follow these steps:

  1. Ensure that the system meets all of the hardware and software requirements specified in "System Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways".

  2. Install Oracle Connect for IMS, VSAM, and Adabas Gateways. See "Installing Oracle Connect for IMS, VSAM, and Adabas Gateways" for instructions.

  3. Configure Oracle Connect for IMS, VSAM, and Adabas Gateways.

    You configure Oracle Connect for IMS, VSAM, and Adabas Gateways through Oracle Studio for IMS, VSAM, and Adabas Gateways. See Oracle Database Gateway for IMS, VSAM, and Adabas Installation and Configuration Guide for Microsoft Windows or Oracle Database Gateway for IMS, VSAM, and Adabas Installation and Configuration Guide for UNIX for details.

2.1 Overview of Oracle Database Gateway for IMS, VSAM, and Adabas

Oracle Database Gateway for IMS, VSAM, and Adabas consists of the following components:

2.2 System Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways

This section provides information about the hardware and software requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways. It contains the following sections:

2.2.1 Hardware Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways

Table 2-1 lists the hardware requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways.

Table 2-1 System Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways

Requirement Value

Processor

An IBM S/390 computer

Memory

The minimum requirement is 4 MB for each connection. A connection is defined as a connection to a server process or daemon. The actual memory requirement depends on such things as the size of the database and the number of databases accessed.

Disk Space (3380 and 3390 disks)

150 cylinders.


2.2.2 Software Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways

Table 2-2 lists the software requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways.

Table 2-2 System Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways

Requirement Value

Operating System

IBM z/OS Series V1R5 or later

IMS/DB

Versions 6.1 or later

OTMA and OTMA C/I

Note: OTMA C/I requires OTMAINIT to be executed.

IMS/DBCTL Access

CICS version 4.1 or later

CICS Transaction Server version 1.3 or later

OTMA and OTMA C/I

Note: OTMA C/I requires OTMAINIT to be executed.

IMS/TM

OTMA and OTMA C/I

Note: OTMA C/I requires OTMAINIT to be executed.

AdabasFoot 1 

Adabas MVS versions 6.2 or later

Adabas UNIXFoot 2  version 2.232 or later

Adabas VMS version 3.22 or later

CICS TP Monitor (when accessing VSAM or IMS/DB data under CICS)

V4R1 or higher (recommended to use CICS V6R1 or later).

CICS EXCI support must be installed and IRCSTRT=YES must be specified in the CICS initialization parameters, so that the IRC (Inter Region Communication) starts.

You can also set the IRC to open by issuing the following command: CEMT SET IRC OPEN. Also the IBM group DFH$EXCI (or an equivalent user-defined group) must be installed in the CICS region - using the CEDA RDO facility.

Oracle Database Gateway

Oracle Database Gateway 11g (11.1.0).


Footnote 1 Oracle certifies its connectivity with the versions listed explicitly. Backward compatibility of higher versions relies on SoftwareAG's backward compatibility policies.

Footnote 2 Only on Oracle-supported UNIX platforms. HP Tru64 and Linux platforms not currently supported for Adabas.

2.3 Accessing the Installation Software

You can access Oracle Connect for IMS, VSAM, and Adabas Gateways by using one of the following methods:

2.3.1 Downloading Oracle Software from the Oracle Technology Network Web Site

This section describes how to download the installation archive files and extract them on your hard disk. It contains the following topics:

2.3.1.1 Downloading the Installation Archive File

To download the installation archive files from the Oracle Technology Network (OTN):

  1. Use any browser to access the software download page on OTN:

    http://www.oracle.com/technology/software

  2. Navigate to the download page for the product that you want to install.

  3. On the download page, identify the required disk space by adding the file sizes for each required file.

    The file sizes are listed next to the file names.

  4. Select a file system with enough free space to store and expand the archive files.

    In most cases, the available disk space must be at least twice the size of all of the archive files.

  5. On the file system that you selected in step 4, create a parent directory for each product, for example, dg4ims, to hold the installation directories.

  6. Download all of the installation archive files to the directory that you created in step 5.

  7. Verify that the files you downloaded are the same size as the corresponding files on OTN.

2.3.1.2 Extracting the Installation Files

To extract the installation archive files:

  1. If necessary, change directory to the directory that contains the downloaded installation archive files.

  2. To extract each file, enter the gunzip command.

    For example:

    $ gunzip filename.cpio.gz

    This command creates files with names similar to the following:

    filename.cpio

  3. To extract the installation files, enter the cpio command.

    For example:

    $ cpio -idmv < filename.cpio

    Note:

    Refer to the download page for information about the correct options to use with the cpio command. Some browsers extract files while downloading them, but leave the .gz file extension. If these steps do not work, remove the .gz extension from the files and repeat step 3.

    For each file, this command creates a subdirectory named Diskn, where n is either 1 or the disk number identified in the file name.

2.3.2 Copying the Oracle Software to a Hard Disk

Before installing Oracle Connect for IMS, VSAM, and Adabas Gateways, you might want to copy the software to the hard disk. This enables the installation process to run a bit faster. Before copying the installation media content to the hard disk, you must mount the installation media. The following section describes how to mount discs and copy their content to the hard disk.

2.3.2.1 Mounting Discs

On most Sun Solaris operating systems, the disc mounts automatically when you insert it into the disc drive. If the disc does not mount automatically, perform the following steps to mount it:

  1. Enter the following command to switch user to root:

    $ su - root

  2. If necessary, enter a command similar to one of the following to eject the currently mounted disc, then remove the disc from the drive:

    On Sun Solaris (SPARC):

    # eject

    On IBM AIX:

    # umount /cdrom

    On HP-UX PA-RISC:

    # /usr/sbin/umount /SD_CDROM

    In these examples, /cdrom and /SD_CDROM are the mount point directories for the disc drive.

  3. Insert the appropriate disc into the disc drive.

  4. To verify that the disc mounted automatically, enter a command similar to the following, depending on your platform:

    Sun Solaris (SPARC):

    # ls /cdrom/cdrom0

  5. If this command fails to display the contents of the disc, enter a command similar to the following to mount it, depending on your platform:

    Sun Solaris (SPARC):

    # /usr/sbin/mount -r -F hsfs /dev/dsk/cxtydzs2 /cdrom

    In this example, /cdrom is the disc mount point directory and /dev/dsk/cxtydzs2 is the device name for the disc device, for example /dev/dsk/c0t2d0s2.

  6. If Oracle Universal Installer displays the Disk Location dialog box, enter the disk mount point directory path, for example:

    /mnt/cdrom

    After you have the Oracle Gateway shiphome image, Oracle Connect for IMS, VSAM, and Adabas Gateways software is located in the following directory:

    /gateways/legacy/Connect.zip

    You can unzip this file on any machine. It includes the following files:

    • ac11000.transmit.kit

    • ac11000.transmit.load

    • brand.bin

2.4 Installing Oracle Connect for IMS, VSAM, and Adabas Gateways

This section explains how to install Oracle Connect for IMS, VSAM, and Adabas Gateways from the CD-ROM. This section includes the following topics:

Note:

The back-end database gateways that run on an IBM z/OS platform are:
  • Oracle Database Gateway for VSAM

  • Oracle Database Gateway for IMS/DB

  • Oracle Database Gateway for Adabas

2.4.1 Installation Worksheet

Verify that you have all the information detailed in Table 2-3 so you can refer to it during the configuration process.

Table 2-3 Preinstallation Information

Topic Required Information Default Comment

General

Operating system

-

IBM z/OS Series V1R0 or later

-

Disk space

-

150 cylinders

-

Memory

-

The minimum requirement is 4 MB for each connection. A connection is defined as a connection to a server process or daemon. The actual memory requirement depends on such things as the size of the database and the number of databases accessed.

-

Installation high-level qualifier

AC10131

-

-

Volume

-

-

-

Unit

3390

SMS only: unit where SMS is located.

-

Output class

A

-

-

JCL job card

-

An optional card (up to 6 lines) to replace the prefix job (entered as it will appear in the job)

-

ISPF load library name

ISP.SISPLOAD

-

CICS

CICS EXCI load library name

CICS.CICS.SDFHEXCL

To access VSAM or IMS/DB data under CICS


2.4.2 Preinstallation Instructions

Before starting the installation, make sure that you have the following information available:

  • The output class for the installation output if you do not want to use the default value A.

  • If you use SMS to manage all datasets, then you cannot provide unit and volume information, which is the unit where SMS is located.

Before starting the installation, make sure that you have the following permissions:

  • Permission to define an APF-authorized library.

  • Permission to write to an active proclib, such as user.proclib.

  • Permission to read the CICS EXCI library when accessing data under CICS.

  • Permission to update the security manager, such as RACF.

  • Optionally, permission to specify an output class for Oracle Connect for IMS, VSAM, and Adabas Gateways output. Assigning a device that is set on HOLD prevents the loss of log information when the started tasks of Oracle Connect for IMS, VSAM, and Adabas Gateways finish.

Oracle Connect for IMS, VSAM, and Adabas Gateways for the IBM z/OS platform is included in the following datasets:

  • [INSTROOT].TRANSMIT.KIT

  • [INSTROOT].TRANSMIT.LOAD

where INSTROOT is the high-level qualifier of the installation, such as AC10131.

2.4.3 Kit Installation Instructions

Perform the following on the mainframe:

  1. Run the following command:

    tso profile noprefix
    

    The user name will not be used as part of the dataset name. On some systems this is the default.

  2. Allocate datasets with the following space for each of these files:

    • [INSTROOT].TRANSMIT.KIT = 130 tracks (3380 and 3390 disks)

    • [INSTROOT].TRANSMIT.LOAD = 500 tracks (3380 and 3390 disks)

    For each dataset: RECFM=FB and LRECL=80. The block size is 3120.

2.4.3.1 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 for IMS, VSAM, and Adabas Gateways 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 ac11000.transmit.kit '[INSTROOT].transmit.kit' (replace

    where:

    • ac11000.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 transfer the data from the .LOAD file to the mainframe computer:

    put ac11000.transmit.load '[INSTROOT].transmit.load' (replace

  7. Close the FTP connection.

2.4.4 Installation Instructions

Perform the following steps to install Oracle Connect for IMS, VSAM, and Adabas Gateways:

  1. From within TSO, run the following command at the TSO prompt:

    RECEIVE INDSNAME('INSTROOT.TRANSMIT.KIT')
    

    where INSTROOT represents the high-level qualifier you want to assign to the Oracle Connect for IMS, VSAM, and Adabas Gateways installation. The default value is AC10131.

    Note:

    You can use more than one high-level qualifier (such as ACME.DEV.AC10131) with the following conditions:
    • The total length must be less than or equal to twenty characters.

    • The words transmit and buildkit cannot be used as high-level qualifiers.

  2. Enter the following command when prompted for the restore parameters:

    da('INSTROOT.TRANSMIT.LIB') [UNIT (unit), VOLUME (volume)]
    

    This extracts the INSTROOT.TRANSMIT.LIB library from the INSTROOT.TRANSMIT.KIT kit to the specified unit and volume. If a unit and volume are not specified, the library is extracted to the current unit and volume.

  3. Run the PREPARE member of the [INSTROOT].TRANSMIT.LIB library:

    ex PREPARE
    

    Follow the instructions in the Response column in Table 2-4 for each entry in the Screen column.

    Table 2-4 Installation Prepare Job Prompts and Responses

    Screen Response

    DO YOU WANT TO USE SMS MANAGED STORAGE FOR THIS INSTALLATION Y/N [N]:

    If you want to manage the storage using SMS, answer Y, otherwise answer N.

    ENTER THE STORCLASS FOR INSTALLATION TEMP DATASETS [ ]:

    This prompt is displayed only if SMS is used to manage the installation (you answered Y to the first prompt).

    Enter the storage class

    ENTER THE UNIT NAME FOR INSTALLATION TEMP DATASETS [3390]:

    If a storage class is not specified, then enter the unit name for temporary datasets used during the installation procedure

    ENTER THE VOLUME NAME FOR INSTALLATION TEMP DATASETS:

    This prompt is displayed only if SMS is not used to manage the installation (you answered N to the first prompt).

    The volume name for temporary datasets used during the installation procedure

    ENTER THE OUTPUT CLASS FOR INSTALLATION OUTPUT [A]:

    Enter the output class only if you do not want the default class used (the default is A)

    DO YOU WANT TO USE THE DEFAULT JOB CARD Y/N [Y]:

    A job card is displayed. If you want to use a replacement card, then it must be entered as it will appear in the job. You can enter up to six lines. Enter a blank card to end input.

    If you do not enter a card, then the Oracle Connect for IMS, VSAM, and Adabas Gateways default card is used.

    DO YOU WANT TO PERFORM A MANUAL (M) OR AUTOMATIC (A) INSTALLATION [A]:

    If you want to review the JCL used to install Oracle Connect for IMS, VSAM, and Adabas Gateways before it is submitted, then respond M for a manual installation.

    PLEASE REVIEW AND SUBMIT FOR EXECUTION THE HLQ.TRANSMIT.LIB(INSTJO)

    This prompt is displayed only if a manual installation is requested (you answered M to the previous prompt).


    The following libraries are generated:

    INSTROOT.BUILDKIT.LOAD
    INSTROOT.BUILDKIT.SRC
    INSTROOT.BUILDKIT.GENDEMO
    

    Where INSTROOT is the high-level qualifier you assigned in step 0.

  4. In the INSTROOT.BUILDKIT.SRC library, run the NAVINST member:

    ex NAVINST
    

    Follow the instructions in the Response column in Table 2-5 for each entry in the Screen column.

    Table 2-5 Installation Prompts and Responses

    Screen Response

    DO YOU WANT TO USE SMS MANAGED STORAGE FOR THIS INSTALLATION Y/N [N]:

    If you want to manage the storage using SMS, then answer Y, otherwise answer N.

    THE SOFTWARE WILL BE INSTALLED UNDER THE HIGH LEVEL QUALIFIER THAT YOU WILL CHOOSE.

    ENTER THE HIGH LEVEL QUALIFIER ["QUALIFIER"]:

    This prompt is displayed only if SMS is used to manage the installation (you answered Y to the first prompt).

    The high-level qualifier for the installation (referred to as INSTROOT throughout this guide).

    You can use more than one high-level qualifier (such as ACME.DEV.VA10). The total length must be less than or equal to twenty characters. The qualifiers can be the same as the ones used for the installation (step 0).

    The words "transmit" and "buildkit" cannot be used as high-level qualifiers.

    ENTER THE STORCLASS FOR TEMP DATASETS ['STORCLASS']:

    This prompt is displayed only if SMS is used to manage the installation (you answered Y to the first prompt).

    Enter the storage class.

    ENTER THE UNIT NAME FOR INSTALLATION TEMP DATASETS [3390]:

    The unit name for temporary datasets used during the installation procedure.

    ENTER THE VOLUME NAME FOR INSTALLATION TEMP DATASETS:

    This prompt is displayed only if SMS is not used to manage the installation (you answered N to the first prompt).

    The volume name for temporary datasets used during the installation procedure.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    ENTER THE OUTPUT CLASS FOR INSTALLATION OUTPUT [A]:

    Enter the output class for Oracle Connect for IMS, VSAM, and Adabas Gateways output. Assigning a device that is set on HOLD prevents the loss of log information when the Oracle Connect for IMS, VSAM, and Adabas Gateways started tasks finish (the default is A).

    ADDING AND UPDATING ORACLE CONNECT CONFIGURATION ON THIS MACHINE, FROM A REMOTE ORACLE ADMINISTRATION CONSOLE, CAN ONLY BE DONE BY SOMEONE DEFINED AS AN ADMINISTRATOR FOR ORACLE CONNECT ON THIS MACHINE.

    ENTER A VALID USER NAME FOR AN ORACLE CONNECT ADMINISTRATOR [ALL]:

    To manage Oracle Connect for IMS, VSAM, and Adabas Gateways on this computer from Oracle Studio for IMS, VSAM, and Adabas Gateways, you need to enter a user account of a user who will have administrative authorization, or press Enter to enable any user to administer Oracle Connect for IMS, VSAM, and Adabas Gateways on this computer. The administrative rights can be changed from within Oracle Studio for IMS, VSAM, and Adabas Gateways after the installation.

    DO YOU WANT TO USE THE DEFAULT JOB CARD Y/N [Y]

    A job card is displayed. If you want to use a replacement card, then it must be entered as it will appear in the job. You can enter up to six lines. Enter a blank card to end input.

    If you do not enter a card, then the Oracle Connect for IMS, VSAM, and Adabas Gateways default card is used.

    DO YOU WANT TO PERFORM A MANUAL (M) OR AUTOMATIC (A) INSTALLATION [A]:

    If you want to review the JCL used to install Oracle Connect for IMS, VSAM, and Adabas Gateways, before it is submitted, then respond M for a manual installation.

    PLEASE REVIEW AND SUBMIT FOR EXECUTION THE DSN1 (INSTJBOR)

    This prompt is displayed only if a manual installation is requested (you answered M to the previous prompt).

    DSN1 is the dataset name where INSTJBOR is located.


2.4.5 Data Source Configuration Instructions

Perform the following steps to configure the different data sources:

  1. In the INSTROOT.BUILDKIT.SRC library, run the following command:

    ex CUSTOCL

  2. Follow the instructions on the screen.

    See Table 2-6 for installation prompts and responses when configuring the VSAM data source.

    See Table 2-7 for installation prompts and responses when configuring the IMS/DB data source.

    See Table 2-8 for installation prompts and responses when configuring the Adabas data source.

    Table 2-6 VSAM Gateway-Specific Installation Prompts and Responses

    Screen Response

    ORACLE CONNECT ADAPTERS CUSTOMIZATION HLQ IS [TEST.OR5021]:

    Specify the high-level qualifier of the installation.

    DO YOU WANT ORACLE CONNECT TO WORK WITH ADABAS (YES/NO) [YES]:

    Answer NO to this prompt.

    DO YOU WANT ORACLE CONNECT TO WORK WITH IMS/DB (YES/NO) [NO]:

    Answer NO to this prompt.

    DO YOU WANT ORACLE CONNECT TO WORK WITH CICS APP ADAPTER (YES/NO) [YES]:

    Answer NO to this prompt.

    THE VSAM DRIVER IS INSTALLED AUTOMATICALLY. DO YOU ALSO WANT ORACLE CONNECT TO WORK WITH VSAM UNDER CICS (YES/NO) [NO]:

    If you want to access VSAM data under CICS, answer YES to this prompt.

    ENTER THE CICS EXCI LOAD LIBRARY NAME [CICSTS13.CICS.SDFHEXCI]:

    This prompt is displayed only if you answered YES to the previous prompt. Enter the EXCI LOAD library name only if you do not want to use the default.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    ENTER THE ISPF LOAD LIBRARY NAME [ISP.SISPLOAD]:

    Enter the ISPF load library name only if you do not want to use the default.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    ENTER THE OUTPUT CLASS FOR INSTALLATION OUTPUT [A]:

    Enter the output class character for the job automatically generated for the installation process.

    DO YOU WANT TO USE THE DEFAULT JOB CARD (Y/N) [Y]:

    A job card is displayed. If you want to use a replacement card, then it must be entered as it will appear in the job. You can enter up to six lines. Enter a blank card to end input.

    If you do not enter a card, then the Oracle Connect for IMS, VSAM, and Adabas Gateways default card is used.


    Table 2-7 IMS/DB Driver-Specific Installation Prompts and Responses

    Screen Response

    ORACLE CONNECT ADAPTERS CUSTOMIZATION HLQ IS:

    Specify the high-level qualifier of the installation.

    DO YOU WANT ORACLE CONNECT TO WORK WITH ADABAS (YES/NO) [YES]:

    Answer NO to this prompt.

    DO YOU WANT ORACLE CONNECT TO WORK WITH IMS/DB (YES/NO) [NO]

    Answer YES to this prompt.

    ENTER DBD LIBRARY NAME [IMS.DBDLIB]:

    Enter the IMS DBD library name for IMS on your system only if you do not want to use the default.

    ENTER PSB LIBRARY NAME [IMS.PSBLIB]:

    Enter the IMS PSB library name for IMS on your system only if you do not want to use the default.

    ENTER RES LIBRARY NAME [IMS.SDFRESL]:

    Enter the IMS RES library name for IMS on your system only if you do not want to use the default.

    ENTER PROC LIBRARY NAME [IMS.PROCLIB]:

    Enter the IMS PROC library name for IMS on your system only if you do not want to use the default.

    ENTER YOUR PSB NAME [HOSPPSB]:

    Enter the PSB name only if you do not want to use the default.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    DO YOU WANT ORACLE CONNECT TO WORK WITH CICS TO ACCESS IMS/DB OR VSAM (YES/NO) [NO]:

    If you want to access IMS/DB data under CICS, answer YES to this prompt.

    ENTER THE CICS EXCI LOAD LIBRARY NAME [CICSTS13.CICS.SDFHEXCI]:

    This prompt is displayed only if you answered YES to the previous prompt. Enter the EXCI LOAD library name only if you do not want to use the default.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    DO YOU WANT ORACLE CONNECT SERVER TO WORK WITH CICS APP ADAPTER (YES/NO) [YES]:

    Answer NO to this prompt.

    ENTER THE ISPF LOAD LIBRARY NAME [ISP.SISPLOAD]:

    Enter the ISPF load library name only if you do not want to use the default.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    ENTER THE OUTPUT CLASS FOR INSTALLATION OUTPUT [A]:

    Enter the output class character for the job automatically generated for the installation process.

    DO YOU WANT TO USE THE DEFAULT JOB CARD (Y/N) [Y]:

    A job card is displayed. If you want to use a replacement card, then it must be entered as it will appear in the job. You can enter up to six lines. Enter a blank card to end input.

    If you do not enter a card, then the Oracle Connect for IMS, VSAM, and Adabas Gateways default card is used.


    Table 2-8 Adabas Gateway-Specific Installation Prompts and Responses

    Screen Response

    ADAPTERS CUSTOMIZATION HLQ IS:

    Specify the high-level qualifier of the installation.

    DO YOU WANT ORACLE CONNECT TO WORK WITH ADABAS (YES/NO) [NO]:

    Answer YES to this prompt.

    ENTER THE ADABAS SVC NUMBER [249]:

    Enter the SVC number only if you do not want to use the default number.

    ENTER THE ADABAS DATABASE NUMBER:

    Enter the number of the Adabas database.

    ENTER THE ADABAS LOAD LIBRARY NAME [ADA622.LOAD]:

    Enter the Adabas load library name only if you do not want to use the default library.

    ENTER THE UNIT FOR ADABAS LOAD LIBRARY [3390]:

    Enter the unit only if you do not want to use the default library. The unit to use is the number that you prepared during the preinstallation.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    DO YOU WANT ORACLE CONNECT TO WORK WITH IMS/DB (YES/NO) [YES]:

    Answer NO to this prompt.

    DO YOU WANT ORACLE CONNECT TO WORK WITH CICS APP ADAPTER (YES/NO) [YES]:

    Answer NO to this prompt.

    THE VSAM DRIVER IS INSTALLED AUTOMATICALLY. DO YOU ALSO WANT ORACLE CONNECT TO WORK WITH VSAM UNDER CICS (YES/NO) [NO]:

    Answer NO to this prompt.

    ENTER THE ISPF LOAD LIBRARY NAME [ISP.SISPLOAD]:

    Enter the ISPF load library name only if you do not want to use the default.

    PLEASE CONFIRM (YES/NO/QUIT) [YES]:

    Confirm the entered details.

    ENTER THE OUTPUT CLASS FOR INSTALLATION OUTPUT [A]:

    Enter the output class character for the job automatically generated for the installation process.

    DO YOU WANT TO USE THE DEFAULT JOB CARD (Y/N) [Y]:

    A job card is displayed. If you want to use a replacement card, then it must be entered as it will appear in the job. You can enter up to six lines. Enter a blank card to end input.

    If you do not enter a card, then the Oracle Connect for IMS, VSAM, and Adabas Gateways default card is used.


The installation is completed. All JCL jobs and REXX procedures are included in the INSTROOT.USERLIB library. INSTROOT is the high-level qualifier for the installation.

2.4.6 Postinstallation Instructions

The following postinstallation tasks must be done to work with Oracle Connect for IMS, VSAM, and Adabas Gateways:

2.4.6.1 Postinstallation Tasks

Perform the following tasks after completing the installation to configure Oracle Connect for IMS, VSAM, and Adabas Gateways:

  • 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 for IMS, VSAM, and Adabas Gateways is installed.

    Using FTP, copy the BRANDBIN file to INSTROOT.DEF.BRANDBIN on the mainframe.

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

    For example, before:

    // PARM='-B START IRPCDINI'
    

    After:

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

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

  • 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:

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

    2. Change the startupScript parameter from ATTSRVR to the new name for the server as follows, where [NEW_NAME] is the new name that you chose for the server:

      <Workspace name="Navigator"
                 startupScript="[NEW_NAME]"
                 serverMode="reusable"
                 ... />
      
    3. Exit and save the change.

    Note:

    If you change the name of the ATTSRV member, make sure to use this new name in all related tasks.
  • Define the LOADAUT library as an APF-authorized library.

    To use the global transactions capability, define every steplib library in the ATTSRVR JCL as an APF-authorized library. Make sure that the libraries are APF-authorized after each IPL.

    If you want to use transactions, make sure that RRS is installed.

    Note:

    To define a data set as APF-authorized, in the SDSF screen, enter the following command, where volume_name is the volume where the data set is allocated:
    "/setprog apf,add,dsn=[data_set_name],volume=[volume_name]"
    

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

    "/setprog apf,add,dsn=[data_set_name],SMS"
    
  • The ATTDAEMN, ATTSRVR, and NVIMSSRV started tasks need permission to use an OMVS TCP/IP stack. The owner must be a user with OMVS segment defined and OMVS UID= 0000000000.

  • In the security manager, such as RACF, create the STARTED class general resource profiles ATTDAEMN, ATTSRVR, and NVIMSSRV. These profiles need to have the following permissions:

    • Permission to issue master console commands.

    • START authority for both profiles.

    • Access to an OMVS segment (that defines access to TCP/IP OMVS sockets).

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

  • The installation includes the data set INSTROOT.DEF.GBLPARMS, which contains global environment information. This data set 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 data set, then you must also change the relevant DD card in the used started tasks and scripts.

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

  • Consult TCP/IP documentation for information about specifying Oracle Connect for IMS, VSAM, and Adabas Gateways as the service using port 2551 in the TCP/IP network services file.

2.4.6.2 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'

INSTROOT is the high-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways 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

2.4.6.3 Setting Up Oracle Connect for IMS, VSAM, and Adabas Gateways for Reentrancy

All Oracle Connect for IMS, VSAM, and Adabas Gateways load modules are reentrant to enable subtasking. Therefore, move INSTROOT.LOAD to the Link Pack Area (LPA), where INSTROOT is the high-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed.

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

Note:

If you intend to use impersonation—the ability of a server to execute in a security context that is different from the context of the process that owns the server—, do the following:
  • Place the INSTROOT.LOAD(ATYSVCW) member in an APF-authorized library outside the LPA.

  • Change the ATTSRVR member (located in the active proclib), by adding the following to the STEPLIB list:

// DD DSN=apf_library,DISP=SHR

Where apf_library is the APF-authorized library outside the LPA where the ATYSCVW member was moved.

2.4.6.4 Configuring Additional Settings for Working with CICS

If you did not set up CICS during the installation, do the following to work with CICS:

  1. Add the DD card that defines the CICS EXCI load library to the steplib of the ATTSRVR started task.

    ATTSRVR is located in both INSTROOT.USERLIB and an active proclib (such as USER.PROCLIB).

  2. Add the CICS EXCI load library to the TASKLIB list of the REXX procedures NAVCMD and NAVSQL of the INSTROOT.USERLIB, as follows:

    ALLOCATE DDNAME(TASKLIB) DA(...[CICS_EXCI_load_library]...) SHR
    
  3. For the IRC (Inter Region Communication) to start, IRCSTRT=YES must be defined in the CICS initialization parameters, as specified in Software Requirements for Oracle Connect for IMS, VSAM, and Adabas Gateways.

  4. By default, Oracle Studio for IMS, VSAM, and Adabas Gateways sets the VTAM netname for CICS data sources to ATYCLIEN.

    You can set up ATYCLIEN by doing one of the following:

    • Use the JCL in the INSTROOT.USERLIB(CICSCONF) member to submit the DFHCSDUP batch utility program to add the resource definitions to the DFHCSD dataset (see the IBM CICS Resource Definition Guide for further details).

    • Use the instream SYSIN control statements in the INSTROOT.USERLIB(CICSCONF) member as a guide to defining the resources online using the CEDA transaction.

  5. If you work intend to work with the IMS-DBCTL data source, initialize the EXCI by using the CDBC transaction.

2.4.6.5 Configuring OTMA for Working with IMS/TM

If you want to use the IMS/DBDC data source, you need to check your OTMA configuration. If the OTMA is not configured, perform the following procedure:

  1. If OTMA is not installed, install it using the IMS INSTALL/IVP Dialog.

  2. Set the startup parameter in the IMS startup procedure to OTMA=Yes.

    In addition, set OTMA-related parameters such as GRNAME= for the XCF group name and OTMANM= for the IMS member name in that XCF group, as in the following example:

    EDIT IMS.PROCLIB(DFSPBIV1) - 01.03command ===>000082 AOIS =,000083 GRNAME=IMSATT01,000084 OTMA=YES,000085 MAXPST=000086 OTMANM=
    
  3. Add an entry in the program properties table (PPT) for the OTMA C/I initialization program by editing the SCHEDxx member of the SYS1.PARMLIB dataset and adding the following entry:

    PPT PGMNAME(DFSYSVI0)     /*PROGRAM NAME =DFSYSVI0 */CANCEL    /*PROGRAM CAN BE CANCELED */KEY(7)    /*PROTECT KEY ASSIGNED IS 7 */SWAP      /*PROGRAM IS SWAPPABLE */NOPRIV    /*PROGRAM IS NOT PRIVILEGED */DSI       /*REQUIRES DATA SET INTEGRITY */PASS      /*CANNOT BYPASS PASSWORD PROTECTION */SYST      /*PROGRAM IS A SYSTEM TASK */AFF(NONE) /*NO CPU AFFINITY */NOPREF    /*NO PREFERRED STORAGE FRAMES */
    
  4. Do one of the following for the SCHEDxx changes to take effect:

    • Execute IPL.

    • Issue the SET SCH= command.

  5. Edit and submit the following JCL procedure to run DFSYSVI0 after the IPL to initialize OTMA C/I:

    //OTMAINIT PROC RGN=3000K,SOUT=A,/PARM1=//*//IEFPROC EXEC PGM=DFSYSVI0,//REGION=&RGN//*//STEPLIB DD DISP=SHR,UNIT=SYSDA,//DSN=IMSVS.RESLIB//*//SYSPRINT DD SYSOUT=&SOUT//SYSUDUMP DD SYSOUT=&SOUT//*
    

    It is recommended to add the step for running this program to the IMS/TM started task.

2.4.6.6 Setting Up Oracle Connect for IMS, VSAM, and Adabas Gateways to Update VSAM, IMS, or Adabas Data

You can set up Oracle Connect for IMS, VSAM, and Adabas Gateways to directly update VSAM, IMS/DB, or Adabas data. The setup procedure depends on whether your data source runs under CICS or not. Perform the relevant task.

To set up Oracle Connect for IMS, VSAM, and Adabas Gateways so that you can update VSAM data from a CICS transaction

Copy the UPDTRNS load module from INSTROOT.LOAD to a CICS user load library and then define the UPDTRNS program under CICS using any available group:

CEDA DEF PROG(UPDTRNS) G(group_name) LANG(C) DA(ANY) DE(ORACLE data source UPDATE PROG)

Where INSTROOT is the high-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed and data source is VSAM.

After defining the UPDTRNS program to a group, install it as follows:

CEDA IN G(group_name)

To set up Oracle Connect for IMS, VSAM, and Adabas Gateways so that you can update IMS/DB data from a CICS transaction

Copy the ATYDBCTL load module from INSTROOT.LOAD to a CICS user load library and then define the ATYDBCTL program under CICS using any available group:

CEDA DEF PROG(ATYDBCTL) G(group_name) LANG(C) DA(ANY) DE(ORACLE data source UPDATE PROG)

Where INSTROOT is the high-level qualifier where Oracle Connect for IMS, VSAM, and Adabas Gateways is installed and data source is IMS.

After defining the ATYDBCTL program to a group, install it as follows:

CEDA IN G(group_name)