Release 9.2.0.1.0 for IBM AS/400
Part Number A97615-01
 Contents |
 Index |
| Oracle Transparent Gateway for DB2/400 Installation and User's Guide Release 9.2.0.1.0 for IBM AS/400 Part Number A97615-01 |
|
Before you begin installation, be sure you have the required hardware and software described in Chapter 3, "System Requirements". This chapter contains the following sections:
Oracle Transparent Gateway for DB2/400 release 9.2.0.1.0 can coexist with any previous version of the product. There are no known conflicts. Oracle Corporation does not support upgrading a previous version gateway to a version 9 gateway. You must reinstall. The various instances of the gateway on a machine have no knowledge of each other, other than through the DB2/400 files against which the gateways are executed, and through the data dictionary tables.
|
WARNING: After the data dictionary tables are installed by a Version 9 Gateway, do not reinstall the data dictionary tables from a Version 4 Gateway or a Version 8 gateway. If this is done by mistake, you can reinstall the Version 9 data dictionary table by using the CRTORADDB command that is described in Chapter 6, "Configuring the Gateway". |
Before installing the gateway, you must:
Log on with a user profile that has *SECADM special authority; user profile QSECOFR has this authority.
Ensure that the system value for the QCRTAUT parameter is not *EXCLUDE. To find the current system value, enter the following from the command line:
WRKSYSVAL QCRTAUT
If the system value is *EXCLUDE, change it to any other less restrictive value to allow installation of the gateway. Remember to change QRCTAUT back to *EXCLUDE after installing the gateway.
The panels below (beginning with Figure 4-1) are shown as they appear when first displayed. Any values on the panel are default values provided by Oracle Corporation. Default values are used unless you change them before going on to the next panel.
The installation procedure defines an OS/400 user ID that is identical to the name of the install library. This user ID is known as the gateway ID. The installation procedure also defines that ID with a user class of *USER, which has *JOBCTL authority. This ID is given authority over the entire library. To do that, the commands executed during installation are:
GRTOBJAUT OBJ(QSYS/gateway-id) OBJTYPE(*LIB) USER(gateway_id) AUT(*ALL) GRTOBJAUT OBJ(gateway-id/*ALL) OBJTYPE(*ALL) USER(gateway_id) AUT(*ALL)
where gateway-id is both the gateway user ID and library name.
The security changes in the first six lines below may be made to allow the gateway to adopt the security authority of the "connect to" user ID. The GRTOBJAUT should be done only if the referenced user (in this case, *PUBLIC), does not already have the indicated authority to the object.
GRTOBJAUT OBJ(QSYS/QWTSETP) OBJTYPE(*PGM) USER(*PUBLIC) AUT(*USE) GRTOBJAUT OBJ(QSYS/QSYGETPH) OBJTYPE(*PGM) USER(*PUBLIC) AUT(*USE) GRTOBJAUT OBJ(QSYS/QSYRLSPH) OBJTYPE(*PGM) USER(*PUBLIC) AUT(*USE)
You can use the EDTOBJAUT command to check the authorities of the three objects. For example, to check the current authority of the QWTSETP program in the QSYS library, use the following command:
EDTOBJAUT OBJ(QSYS/QWTSETP) OBJTYPE(*PGM)
If the *PUBLIC line shows *USE, then no change is needed.
Insert the CD-ROM into the AS/400 CD-ROM drive.
Enter the command:
LODRUN drive
where drive is the name of the CD-ROM drive where you mounted the product CD-ROM. The panel in Figure 4-1 is displayed.
Install Oracle Transparent Gateway
You must fill in the Instance name. Use the default name of ORACLE or enter a name from one to six characters long.
The installation procedure either creates a new library, uses a pre-existing, but empty, library, or uses a pre-existing library that has been created using the DB2/400 SQL command CREATE COLLECTION. If the library does not fit into this scenario, then it will not be used. Refer to Figure 4-1. The library must contain no objects other than those objects that were created by the CREATE COLLECTION command.
The preferred method is to use STRSQL to create a DB2/400 collection and then install the gateway into the library that is associated with that collection. Objects that are created later in the collection will be automatically journalled.
________________________________________________________________________________ Install Oracle Transparent Gateway at 9.2.0.1.0 Type Choices, press Enter. Instance name............. ORACLE Name (up to six characters) ===> F1=Help F4=Prompt F9=Retrieve F10=Additional parameters F12=Cancel (C) COPYRIGHT ORACLE CORPORATION, 1994, 2002 ________________________________________________________________________________
After entering a name, press [Enter]. The panel in Figure 4-2 appears.
________________________________________________________________________________ Install Oracle Transparent Gateway at 9.2.0.1.0 System: AS400A Type Choices, press Enter. Instance name..................... ORACLE Name (up to six characters) Instance password................. ORACLE 1-10 characters Prestart jobs..................... *YES *YES, *NO TCP/IP port number................ 1521 1024-65534 Recovery user profile............. ORACLE Name Recovery user password............ ORACLE 1-10 characters Auxiliary storage pool id......... 1 1-16 Install Data Dictionary Support... *YSE *YES, *NO ===> F1=Help F4=Prompt F9=Retrieve F12=Cancel (C) COPYRIGHT ORACLE CORPORATION, 1994, 2002 ________________________________________________________________________________
You may change the choices:
|
Choice Name |
Description |
|---|---|
|
|
is a name from one to six characters long. The default is ORACLE. |
|
|
is the password for the user ID (same as OS/400 User Profile) that is created during installation. The user ID has the same name as the instance name. |
|
|
prestarts the TCP/IP jobs. Use *YES to prestart the TCP/IP jobs, or *NO to prestart NO jobs. You can change how many jobs are prestarted by changing the value of the initial number of TCP/IP jobs parameter by using the CHGORAPJE command. For more information, refer to "CHGORAPJE, Change Prestarted Job Parameters". |
|
|
is 1521, which is the default. If port 1521 is unavailable, enter a different port number. Each instance requires a unique port number. |
|
|
is a profile name you enter, or use the default of the gateway instance name. |
|
|
is a password for the recovery user profile. The default is the gateway instance name. This password must be kept in synchronization with the gateway password. Refer to "CHGRECOPRF, Change Recovery Profile Parameters" |
|
|
uses the default of 1 or you can enter another ID. |
|
|
turns on data dictionary installation. The default is YES. Installation of the data dictionary view support lengthens the installation process. There is only one Transparent Gateway data dictionary for the entire AS/400 machine. All Transparent Gateway instances use the same data dictionary. The data dictionary is created in the library OTGDB2. |
After filling in the choices press [Enter] to continue.
Verify Oracle Install
Enter *YES and press [Enter] to continue the installation process.
________________________________________________________________________________ Verify Oracle Install at 9.2.0.1.0 System: AS400A Verify that you want to install the product. Once this process has started, it will create a library and other objects with the name of the instance specified below. Enter *YES to verify this operation before it is started. New instance name ......... ORACLE enter *YES to verify....... *NO *NO, *YES ===> Bottom F1=Help F4=Prompt F9=Retrieve F12=Cancel (C) COPYRIGHT ORACLE CORPORATION, 1994, 2002 ________________________________________________________________________________
If you entered *YES, a message displays on the screen about 5 to 15 minutes later to let you know the installation is finished. Check the job log for error messages. Use this command:
DSPJOBLOG
Enter the command:
STRSBS instance_name/instance_name
where instance_name is the name used in Step 3.
Installation of the gateway is complete.
Oracle Corporation recommends performing these post-installation steps. If you have more than one instance of the gateway, repeat the steps for each one. Note that you only need to install data dictionary support once. Refer to the table of installation choices in "Step 3: Set Required Parameters" for more information on data dictionary support.
Journalling is the process of recording changes made to files on the AS/400 to ensure transactional consistency. Every table on the AS/400 that is going to be changed must be journalled. Changes to a file are recorded by a JOURNAL in a JOURNAL RECEIVER. Journalling is not required for gateways that are used for read-only purposes.
By default, the gateway runs under commitment control change (*CHG). This means that:
You can change the isolation level from the default setting, *CHG, to cursor stability (*CS). With cursor stability:
Refer to "CHGORATUN, Change Initialization Parameters" for additional information about changing the isolation level.
For information about the *RR setting and more information about *CS and *CHG, refer to the Isolation Level section of the IBM reference for DB2/400.
To verify installation and find out what version of the gateway is running, use this command:
DSPPGM <instance_name>/GTW
where:
instance_name
GTW
The Text Description line resulting from the DSPPGM command informs you of the gateway version.
You can also find out what version of the gateway is running by looking in the job logs for the RUNORAGTTP job.
Journal all AS/400 files changed through the gateway. To start journalling for a file, use the STRJRNPF command. To use the STRJRNPF command, you must have previously created a journal and a journal receiver, as illustrated in the following example. Note that if you installed the gateway into a library created as a SQL collection, then the journal and journal receiver already exist. You do not need to explicitly journal files that are created in a library that is part of a DB2/400 SQL collection. You can journal many files to the same pair of journal and journal receiver.
CRTJRNRCV JRNRCV(instance/QSQJRNRCV) CRTJRN JRN(instance/QSQJRN) JRNRCV(instance/QSQJRNRCV) STRJRNPF FILE(library/file) JRN(instance/QSQJRN)
where:
instance
library
file
is the name of the file you are journalling.
This step is only required if:
Journal the ORACLE2PC physical file, which records two-phase commit transactions. You must journal this file before issuing a distributed transaction to the AS/400. To journal the file enter:
STRJRNPF FILE(instance_name/ORACLE2PC) JRN(library/journal)
where:
instance_name
library
journal
Configure Oracle Net on the Oracle9i database server. Refer to Chapter 5, "Oracle Net" for more information.
The gateway is shipped with IBM observability. Removing observability reduces gateway program object size by approximately 60 percent. If disk space is a concern, and if you have no plans to upgrade to a higher version of OS/400, then Oracle Corporation recommends that you remove observability from the gateway.
To remove observability, perform these steps:
ENDSBS instance_name *IMMED
where instance_name is the name given to the gateway when it is installed.
SBMJOB CMD(CALL instance_name/REMOVEOBS PARM(instance_name))
The gateway subsystem and listener default to an AS/400 priority level of 50 during the installation process. In many cases, a priority level of 50 is conducive to performing the functions provided by the gateway. However, if the AS/400 is running at a high CPU capacity with several jobs competing for CPU allocation, it might be necessary to raise the priority of the gateway subsystem and listener to meet your performance requirements.
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|
