PK
>Aoa, mimetypeapplication/epub+zipPK >A iTunesMetadata.plist
artistNameOracle Corporationbook-infocover-image-hash720925562cover-image-pathOEBPS/dcommon/oracle-logo.jpgpackage-file-hash901673609publisher-unique-idE12078-01unique-id875168873genreOracle DocumentationitemNameOracle® Database Gateway for APPC Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64, 11g Release 2 (11.2)releaseDate2009-07-30T16:20:33Zyear2009
PKv:Z0 PK >A META-INF/container.xml
PKYu PK >A
OEBPS/ch8.htmQ7
Configuring the SNA Communication Package on HP-UX
8 Configuring the SNA Communication Package on HP-UX
Oracle Database Gateway for APPC uses the SNA Advanced Program to Program Communication (APPC/LU6.2) protocol to communicate with an online transaction processing (OLTP). HP-UX system support for APPC is provided by the SNAPlus2 product.
This chapter describes how to set up and configure SNAPlus2 on a HP-UX system to run Oracle Database Gateway for APPC.
Many OLTPs provide options for manipulating the security conduct of an inbound (client) APPC session request. Refer to the appropriate documentation for your OLTP for detailed information about this topic.
Note that for CICS, one security option is not supported by the gateway: ATTACHSEC=PERSISTENT, specified on the CICS CONNECTION definition, requires capability that is not yet available in the gateway.
ATTACHSEC=LOCAL, ATTACHSEC=IDENTIFY, ATTACHSEC=VERIFY, and ATTACHSEC=MIXIDPE are fully supported by the gateway.
8.1.1 Steps for Configuring the Communications Interfaces
To configure the communications interfaces, do the following:
Create SNAPlus2 profiles for the gateway.
Create SNA definitions for the gateway.
Test the configuration.
8.2 SNAPlus2 Configuration Tool
All SNAPlus2 product configuration is done using the xsnapadmin program. xsnapadmin is an X-Windows application that provides a graphical interface to view and modify the current SNAPlus2 configuration and the current running state of the host SNA node. Refer to vendor documentation for more information about using xsnapadmin.
8.3 Creating SNAPlus2 Profiles for the Gateway
Oracle Database Gateway for APPC requires a stored set of definitions, called Side Information Profiles, to support connections between the gateway and remote server. Each profile consists of a profile name and a profile type, which is a set of fields describing the profile. The fields in a profile type are generally a mix of operating parameter values and names of other SNA profiles relevant to the profile. Each functional part of APPC, such as Mode, Remote Transaction Program name and Logical Unit (LU), is described by a distinct profile type.
8.4 Independent Versus Dependent LUs
Oracle recommends independent LUs for the gateway because they support multiple parallel sessions or conversations. This means multiple Oracle client applications can be active simultaneously with the same OLTP through the independent LU.
Dependent LUs only support a single active session. SNAPlus2 queues additional conversation requests from Oracle Database Gateway for APPC behind an active conversation. That is, conversations are single-threaded for dependent LUs.
If a dependent LU is correctly defined, no alterations are needed for the gateway configuration, to the host transaction, or to how the OLTP is started.
The operational impact of dependent LUs is that the first client application can initiate a conversation through the gateway with the OLTP, and while that transaction is active (which could be for seconds, minutes, or hours, depending on how the client application and transaction are designed), any other client application initiating a conversation with the same OLTP instance appears to hang as it waits behind the previous conversation.
If a production application really only uses a single conversation or transaction at any one time, there should be no impact.
However, additional concurrent conversations or transactions might be required for testing or other application development. Each requires that additional dependent LUs be defined on the remote host in addition to an SNAPlus2 configuration file entry that defines the additional dependent LUs on the HP-UX workstation. The TIP that initiates the conversation must specify the different SNAPlus2 Partner LU through a different Side Information Profile. Refer to the PGAU DEFINE TRANSACTION SIDEPROFILE parameter in Chapter 2 of Oracle Database Gateway for APPC User's Guideand the SNAPlus2 Symbolic Destination Name discussed in the section, "Sym Dest Name".
In some uses of the gateway, independent LUs cannot be used. For example, with the IMS LU6.1 Adapter for LU6.2, parallel sessions are not supported. In this case, multiple concurrent sessions with the IMS LU6.1 Adapter for LU6.2 can be achieved by defining a pool of dependent LUs. For each dependent LU, select the "LU in the pool of default LUs" option. When a conversation is requested, an available local LU from the default LU pool is assigned automatically by SNAPlus2. For more information, refer to vendor documentation.
8.4.1Sym Dest Name
This option lets you enter the side information associated with a particular symbolic destination name. You can use an alphanumeric string up to 8 characters as the Sym Dest Name. The symbolic destination name is referred to as the side information profile in other parts of this guide. This name is specified by the SIDEPROFILE keyword in the DEFINE TRANSACTION statement used to define your transaction to PGAU.
The Partner TP name field specifies the name of the transaction to be run on the OLTP side of the conversation. This field must be specified, but the TP name can be overridden by the gateway at conversation startup.
The Partner LU field specifies the LU name of the OLTP on the remote host. The Mode Name field specifies the mode name to be used for conversations with the specified OLTP.
The security information that can be specified in this menu is not usable for the gateway. The security parameters are always set by the gateway based on gateway initialization parameters.
8.5Creating SNA Definitions for the Gateway
SNAPlus2 definitions are stored in the following files, which are located in the /etc/opt/sna directory:
SNA node definitions: sna_node.cfg
SNA domain definitions: sna_domn.cfg
These files are created and maintained with the xsnapadmin tool. Maintenance of the SNA definitions is normally done by a user with administrative authority. The following information is intended for the person creating SNA definitions for the gateway. You should have some knowledge of SNA before reading this section.
8.6 Sample SNAPlus2 Definitions
The gateway $ORACLE_HOME/dg4appc/sna subdirectory contains a set of sample SNAPlus2 definitions for the gateway, created with the xsnapadmin. SNA definitions are very specific to the HP 9000 host and SNA network. Because of this, these sample definitions will not work without being tailored for the local host and SNA network.
8.7 Configuring SNAPlus2
This section describes the process of creating SNA definitions for SNAPlus2 using the xsnapadmin tool. All configuration is done using the various dropdown menus and panels in xsnapadmin. The configuration descriptions in the steps below follow the samples provided. You must tailor the various SNA values for your local host and SNA network.
Step 1 Starting xsnapadmin
Use the following commands to run xsnapadmin. The DISPLAY environment variable must be appropriately set. If you are running xsnapadmin from the local HP 9000 console, then DISPLAY should already be set. If you are running xsnapadmin from a remote X display, then set DISPLAY to the host name or IP address of that display.
At xsnapadmin startup, the main screen opens and displays the current configuration of the local SNA node.
Step 2 Configuring the SNA Node
On the main screen of xsnapadmin, pull down the Services menu and select Configure Node Parameters.
In the Node Parameters dialog box, enter the APPN support type, the Control Point Name, Control Point, and Node ID as needed. The Control Point Name is composed of the SNA Network Name and the CP name of the local host.
Click OK.
Step 3 Adding a Port
From the Service menu, select Connectivity and then select Add Port.
In the Add to nodename dialog box, select the Port and type you are using and click OK.
In the subsequent SAP dialog box, enter a Port name and network card number. The Port name is used to logically name the physical network card you are using and to bind a Service Access Port to the card for SNA protocols. Usually, you can accept the values provided in the dialog box. If a different network card is needed, however, enter the card number as reported with the lanscan command.
Click OK.
Step 4 Create a Link Station
When the Port has been defined, you need to create a Link Station. The Link Station represents the SNA node of the remote host of the APPC server. But before you can create the Link Station, you must create a Remote Node definition.
From the Services menu, select APPC and select Add Remote Node.
In the Remote Node dialog box, enter the SNA CPNAME of the remote node and click OK.
Now you are ready to create the Link Station. From the Services menu, select Connectivity and select Add Link Station. In the dialog box that is displayed, select the Port previously defined and click OK.
In the Link Station dialog box, enter a name for the Link Station, choose the SNA Port name, and choose the type of link activation.
Choose the LU Traffic type. For maximum flexibility, choose the Any option.
For Independent LU traffic, specify the Remote Node name.
Click on Remote Node and select the node you previously created. Click OK.
For Dependent LU traffic, specify the Local Node ID, and optionally, Remote Node ID. Then, specify the Contact Information. Contact information contains the MAC address of the remote host as well as the SAP number. Click Advanced for additional parameters of the Link Station.
The Ethernet Parameters screen shows additional parameters of the Link Station. These parameters affect initial XID contact and retransmission times and limits. You need not change the default values. Click OK.
Step 5 Create Local LUs
When the Remote Node definitions have been made, create the Local LU names for the local host. From the Services menu, select APPC and Add Local LU.
In the Local LU dialog box, enter the name of the local LU and an alias. This name must correspond to the VTAM definitions on the remote server host for the HP 9000 host.
Click OK.
Step 6 Create Partner LUs
Now define a Partner LU that represents the LU that the remote server is using to communicate. From the Services menu, select APPC and Add Partner LUs and Partner LU on Remote Node.
In the dialog box that is displayed, enter the Partner LU name and characteristics. The Partner LU name will contain the SNA Network Name as well as the LU name of the remote LU.
Enable parallel session support. The location is the name as the Remote Node name. You can click on Location for a list.
Click OK.
Step 7 Create Mode and CPI-C Profiles
Once the local and remote LU definitions have been made, create the necessary Mode and CPI-C definitions. From the Services menu, select APPC and Modes.
In the Modes dialog box, click on Add to add a new mode.
In the subsequent Mode dialog box, enter the Mode Name and other session parameters. The recommended name for an APPC mode is ORAPLU62. Contact your Remote Host system administrator for an appropriate mode parameter name.
Click OK.
Now that the Mode has been defined, create the CPI-C Side Information Profile, which the gateway will use as a connection name. From the menu, select APPCandCPI-C. In the CPI-C destination names dialog box, click on Add to add a new profile.
In the CPI-C destination dialog box, enter the Profile name, Partner TP, Partner LU, mode, and Security option. The partner TP name is the name of the host transaction program or a dummy value to be overridden in the TIP.
For the Partner LU, enter either the full LU name or the alias created previously. Enter ORAPLU62 for the mode name.
Lastly, choose the type of security these sessions will use. This affects how session authorization is done.
Click OK.
8.8 Testing the Connection
Ensure that your connection is working. Do this by starting the SNAPlus2 Node and then starting the individual link stations.
Figure 8-1 shows the relationship between SNAPlus2 definitions and the VTAM definitions on the remote host.
Figure 8-1 Relationship Between SNAPlus2 Definitions and Remote Host Definitions
The hardware requirements for this release of the gateway on your platform are described in the following sections:
Table 3-1 lists the minimum hardware requirements for Oracle Database Gateway fro APPC.
Table 3-1 Hardware requirements for Oracle Database Gateway for APPC
Hardware Items
Required for AIX-Based System
Required for HP-UX Itanium
Required for Solaris Operating System (SPARC)
Required for Linux x86
Required for Linux x86 64 bit
Temporary Disk Space
190 MB
415 MB
180 MB
80 MB
120 MB
Disk Space
3 GB
3.5 GB
2 GB
1 GB
1.2 GB
Physical Memory*
512 MB
512 MB
512 MB
512 MB
512 MB
Swap Space
150 MB
150 MB
150 MB
150 MB
150 MB
Processor
IBM RS/6000 AIX-Based System Processor
HP Itanium processor for hp-ux 11
Sun Solaris Operating System (SPARC) Processor
x86
x86_64
The following factors affect the virtual memory requirements of the gateway server process:
Number of concurrent gateway connections open by each user
Number of data items being transferred between the gateway and the remote transaction program
The Oracle Net protocol adapters that were included during the gateway installation
Additional factors, such as configured network buffer size
3.1.1 Network Attachment Requirements
The gateway requires any network attachment supported by either the SNA communication package for your platform or the TCP/IP Networking Facility for TCP/IP communication.
However, if you are using only the new TCP/IP support for IMS Connect feature, you will not need an SNA package. Your operating system comes with TCP/IP installed.
3.2 Software Requirements
The system software configuration described in this section is supported by Oracle, provided that the underlying system software products are supported by their respective vendors. Verify the latest support status with your system software vendors.
Refer to the Oracle Database Installation Guide and to the certification matrix on My Oracle Support for the most up-to-date list of certified operating system version requirements to operate the gateway for your Linux for Intel Pentium-based 32-bit systems, AIX-Based, HP-UX or Solaris system. The My Oracle Support Web site is available at
Each operating system uses specific communications servers, as described in this section.
Note:
If you choose to use TCP/IP support for IMS Connect as communication protocol, then you do not need to use an SNA communication package from the following list. Each operating system comes with a TCP/IP protocol automatically installed. If you choose to use the TCP/IP protocol, then you need to configure it to work properly with the gateway. Refer to Chapter 12, "Gateway Configuration Using TCP/IP Communication Protocol".
Communications Protocols for Linux for Intel Pentium-based 32-bit Systems
Communications protocols for Linux for Intel Pentium-based 32-bit System IBM Communications Server V6.0.1.1 for Linux or higher, or the TCP/IP communication software that comes with your operating system.
Communications Protocols for AIX-based Systems
SNA Server for AIX version 6.01 or higher, or the TCP/IP communications software that comes with your operating system.
Communications Protocols for HP-UX
HP-UX SNAPlus2 Link Release 11.x and HP-UX SNAPlus2 API Release 11.x or higher or the TCP/IP communications software that comes with your operating system.
Communications Protocols for Solaris
SNAP-IX version 6 or higher, or the TCP/IP communications software that comes with your operating system.
3.2.3 Oracle Database Requirements
All UNIX platforms require that the Oracle database, that is to act as the Oracle database be up to date with the latest patchset for supported Oracle database releases.
In addition to the other software requirements of the gateway and the platform being used, the following list outlines other requirements necessary on the IBM mainframe:
OLTP for SNA
The OLTP must support mapped APPC conversations. If the OLTP transaction programs to be executed through the gateway perform database updates, then the APPC verbs CONFIRM, CONFIRMED, and SEND_ERR must be supported by the OLTP. These verbs implement APPC SYNCLEVEL 1.
All resources controlled by an OLTP that can be updated by transaction programs invoked through the gateway must be defined as recoverable resources to the OLTP and host system if COMMIT/ROLLBACK capability is required for those resources. For example, a VSAM file updated by a CICS transaction must be defined to CICS as a recoverable file for COMMIT/ROLLBACK to control the updates.
The gateway is compatible with all supported releases of SNA-enabled products such as CICS, IMS/TM, IDMS and z/OS.
Note:
For a list of known restrictions, read the "Known Restrictions" section before proceeding with the installation of the gateway.
OLTP for TCP/IP
IMS/TM: Release 7.1 or later is required, as well as any APARs (patches) listed in the IBM IMS Connect Guide and Reference.
IMS Connect: Release 1.2 or higher is required.
PK9 8 PK >A OEBPS/ch11.htm:U
Configuring the OLTP
10 Configuring the OLTP
The following sections describe how to configure the online transaction processing OLTP.
On a gateway using TCP/IP support for IMS Connect, you must specify EDIT=ULC in the IMS TRANSACT macro if you need input case sensitivity. When you are using SNA support, you do not need to specify EDIT=ULC in the IMS TRANSACT macro.
10.1 Configuring the OLTP for an SNA Environment
The steps for configuring OLTP to communicate with the Oracle Database Gateway for APPC vary depending on which OLTP you are using and on which platform the OLTP is running. CICS Transaction Server for z/OS, IMS/TM, APPC/MVS, and z/OS are the currently supported OLTPs. Choose the instructions corresponding to your OLTP from the following sections:
You need to perform the configuration steps for an OLTP only if this is the first time that you are configuring that OLTP.
10.1.1Configuring CICS Transaction Server for z/OS
If your OLTP is CICS Transaction Server for z/OS, then perform the following steps to configure it for communication with the gateway:
Configure MVS VTAM for the SNA communication package that will make the APPC connection to your system. At least one independent LU must be available to the gateway.
Check the VTAM logmode table used by the CICS Transaction Server for z/OS. (The table name is specified in the MODETAB parameter in the VTAM APPL definition for CICS.) Ensure that an entry exists for APPC sessions with parallel session and sync-level support.
The oraplu62.asm file in the $ORACLE_HOME/dg4appc/sna directory contains a sample mode entry, including comments that indicate the required values in the mode entry.
Using a file transfer facility, transfer the following files from the $ORACLE_HOME/dg4appc/demo/CICS directory to the z/OS system on which you run CICS Transaction Server for z/OS:
dfhcsdup.jcl: JCL to run the CICS DFHCSDUP utility
pgaflip.asm: Assembler source for the CICS FLIP transaction
pgaflip.jcl: JCL to assemble and linkedit the CICS FLIP transaction
Using the comments in the dfhcsdup.jcl file, tailor the JCL and input statements to match your system setup, and submit it for batch execution. Performing this step updates your Transaction Server for z/OS system definitions.
Using the instructions in the pgaflip.jcl file comments, tailor the JCL to match your system setup, and submit it for batch execution. Performing this step assembles and linkedits the pgaflip.asm file into a load module library accessible to your Transaction Server for z/OS through the DFHRPL DD statement in the CICS startup procedure.
Log on to your CICS Transaction Server for z/OS and enter the following transaction:
CEDA INSTALL GROUP(ORAPGA)
This transaction installs the CICS connection and session definitions for APPC communication with the gateway on UNIX. It also installs definitions for the sample CICS programs and transactions provided with the gateway.
Your CICS Transaction Server for z/OS configuration is now complete.
10.1.2 Configuring IMS/TM
If your OLTP is IMS/TM, then perform the following steps to configure IMS/TM and z/OS for communication with the gateway:
Configure your IMS system for the APPC.
Configure MVS VTAM for the SNA APPC connection to UNIX. At least one independent LU must be available for use by the gateway, unless you are using the IMS LU6.1 Adapter for LU6.2 applications. In this case, you must have one dependent LU defined for each concurrent session. For example, if you want to support 10 concurrent sessions, then you must have 10 dependent LUs defined.
Check the VTAM logmode table used by IMS/TM. The table name is specified by the MODETAB parameter in the VTAM APPL definition. For APPC/IMS, ensure that an entry exists for APPC sessions with sync-level support and parallel session support. The oralu62.asm and oraplu62.asm files in the $ORACLE_HOME/dg4appc/sna directory contain sample mode entries for single session and parallel session support, respectively. The samples include comments that indicate the required values in the mode entries.
Using your file transfer facility, transfer the following files from the $ORACLE_HOME/dg4appc/demo/IMS directory to the z/OS system on which you run IMS/TM:
pgaflip.asm is assembler source for IMS FLIP transaction
pgaflip.jcl is JCL to assemble and linkedit IMS FLIP transaction
imsgen.asm is IMS stage 1 gen definitions for the IMS FLIP transaction
Add the statements in the imsgen.asm file to your IMS stage 1 gen and run your IMS stage 1 and stage 2 gens. Use the online change utility to enable the new transaction definition.
Using the comments in the pgaflip.jcl file, tailor the JCL to match your system setup and submit it for batch execution. This assembles and linkedits the pgaflip.asm file into a load module library that is accessible to your IMS/TM system and creates an PSB and an ACB for the FLIP transaction.
Perform the tasks necessary on your system to make the new transaction available to IMS/TM. Depending on your system setup, you might have to restart IMS.
The IMS/TM configuration is now complete.
10.1.3Configuring APPC/MVS
If your OLTP is APPC/MVS, then perform the following steps to configure APPC/MVS for communication with the gateway:
Configure MVS VTAM for the SNA APPC connection to HP-UX. At least one independent LU must be available for use by the gateway.
Check the VTAM logmode table used by APPC/MVS. (The table name is specified by the MODETAB parameter in the VTAM APPL definition for APPC/MVS.) Ensure that an entry exists for APPC sessions with SYNCLEVEL and parallel session support. The oraplu62.asm file in the $ORACLE_HOME/dg4appc/sna directory contains a sample mode entry, including comments that indicate the required values in the mode entry.
Allocate a partitioned data set (PDS) on your z/OS system where the sample files are placed. The PDS should be allocated with RECFM=FB, LRECL=80, and a BLKSIZE appropriate for the device type on which it is located. Approximately two tracks of 3390 disk space are required with one directory block. Oracle suggests naming this partitioned data set (PDS) ORAPGA.APPCMVS.SAMPLIB.
Using a file transfer facility, transfer the following files from the $ORACLE_HOME/dg4appc/demo/MVS directory to the z/OS PDS you allocated in the previous step, using the following specified member names:
pgaflip.jcl: JCL to add an APPC/MVS TP profile and to define the execution environment for the transaction. Store this file in your z/OS PDS as member PGAFLIPJ.
pgaflip.rex: The REXX source for the APPC/MVS PGAFLIP transaction. Store this file in your z/OS PDS as member PGAFLIP.
Using the comments in the pgaflip.jcl file, tailor the JCL to match your system setup and submit it for batch execution. Performing this step defines the APPC/MVS TP profile for the PGAFLIP transaction and stores it in the APPC/MVS profile data set. Ensure that you change the data set name in the JCL to match the name of the z/OS PDS allocated in Step 3.
10.2 Configuring the OLTP for a TCP/IP Environment
These are the steps for configuring OLTP to communicate with Oracle Database Gateway for APPC using TCP/IP for IMS Connect. IMS/TM, through IMS Connect, is the only supported OLTP for this release of the gateway.
Perform the following steps to configure IMS/TM and z/OS for communication with the gateway:
Configure your IMS system.
Configure IMS Connect
For information on how to configure IMS Connect, refer to the IBM manual, IMS Connect Guide and Reference.
Using a file transfer facility, transfer the following files from the $ORACLE_HOME/dg4appc/demo/IMS directory to the z/OS system on which you run IMS/TM:
pgaflip.asm: Assembler source for IMS FLIP transaction
pgaflip.jcl: JCL to assemble and linkedit IMS FLIP transaction
imsgen.asm: IMS stage 1 gen definitions for the IMS FLIP transaction
Add the statements in the imsgen.asm file to your IMS stage 1 gen and run your IMS stage 1 and stage 2 gens. Use the online change utility to enable the new transaction definition.
Using the comments in the pgaflip.jcl file, tailor the JCL to match your system setup and submit it for batch execution. This assembles and linkedits the pgaflip.asm file into a load module library that is accessible to your IMS/TM system and creates an PSB and an ACB for the FLIP transaction.
Perform the tasks necessary on your system to make the new transaction available to IMS/TM. Depending on your system setup, you might have to restart IMS.
PK[pT O PK >A OEBPS/title.htm
Oracle Database Gateway for APPC Installation and Configuration Guide, 11g Release 2 (11.2) for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64
Oracle® Database Gateway for APPC
Installation and Configuration Guide
11g Release 2 (11.2)for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64
E12078-01
July 2009
Oracle Database Gateway for APPC Installation and Configuration Guide, 11g Release 2 (11.2) for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64
Contributor: Vira Goorah, Govind Lakkoju, Peter Wong, Juan Pablo Ahues-Vasquez, Peter Castro, and Charles Benet
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
PKE PK >A
OEBPS/ape.htm,H
Configuration Worksheet
D Configuration Worksheet
Table D-1 lists the parameter names and the reasons you will need them to configure the gateway and the communications interface you have chosen (either SNA or TCP/IP). You can use this table as a worksheet to gather the specific information you need before you begin the configuration process.
Ask your systems administrator to provide you with any parameter names you do not know.
Table D-1 Parameters for Configuring Gateway and Communication Protocols
Name of Parameter Needed
Purpose
Your Specific Parameters Here
ORACLE_HOME
For: gateway's Oracle home
_______________________________
ORACLE_SID
For: gateway's system ID
_______________________________
Any Security Options Needed
For: SNA remote LU properties options
_______________________________
Appropriate Name for Each Side Information Profile
for: SNA creating CPI-C symbolic destination names (side information profiles), general information
_______________________________
Appropriate Mode
For: SNA
______________________________
TP Name
For: SNA partner information in CPI-C name properties
_______________________________
Partner LU Name Alias
For: SNA partner information in CPI-C name properties
______________________________
Unique Side Profile Name
For: Configuring TCP/IP support for IMS Connect
______________________________
Remote Host name or TCP/IP Address
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_______________________________
IP Address
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_______________________________
IMS Connect Port Number
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_______________________________
Conversational Protocol (Y/N)
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_______________________________
Timer choice:
a) .25
b) .01 to .25
c) Does not exist
d) Receives wait
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_______________________________
Socket Connection Type Choice:
a) Transaction
b) Persistent
c) Nonpersistent
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
______________________________
IMS Client ID Name
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
______________________________
IMS Commit Mode Choice:
a) 0
b) 1
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_____________________________
IMS Destination ID, data store name
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_____________________________
LTERM
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
______________________________
RACF Group Name
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_____________________________
IRM_ID
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_____________________________
LLLL (Y/N)
For: Configuring TCP/IP support for IMS Connect, pg4tcpmap tool
_____________________________
PKdټ, , PK >A
OEBPS/ch1.htmvT
Introduction to Oracle Database Gateway for APPC
1 Introduction to Oracle Database Gateway for APPC
The Oracle Database Gateway for APPC (the gateway) enables users to initiate transaction program execution on remote online transaction processors (OLTPs). The Oracle Database Gateway for APPC can establish a connection with OLTP using the SNA communication protocol. The gateway can also use TCP/IP for IMS Connect to establish communication with the OLTP through TCP/IP. The gateway provides Oracle applications with seamless access to IBM mainframe data and services through remote Procedural Call (RPC) processing. The gateway can access any application capable of using the CPI-C API either directly or through a TP monitor such as CICS.
This chapter discusses the architecture, uses and features of the gateway. It contains the following sections:
The Oracle Database Gateway for APPC extends the RPC facilities available with the Oracle database. The gateway enables any client application to use PL/SQL to request execution of a remote transaction program (RTP) residing on a host. The gateway provides RPC processing to systems using the SNA APPC (Advanced Program-to-Program Communication) protocol and to systems using TCP/IP for IMS Connect protocol. This architecture allows efficient access to data and transactions available on the IBM mainframe and IMS, respectively.
The gateway requires no Oracle software on the remote host system. As a result, the gateway uses existing transactions with little or no programming effort on the remote host.
Note:
For gateways using SNA only the use of a generic and standard protocol, APPC, enables the gateway to access a multitude of systems. The gateway can communicate with virtually any APPC-enabled system, including IBM Corporation CICS on any platform, IBM Corporation IMS and APPC/MVS. These transaction monitors provide access to a broad range of systems, allowing the gateway to access many datastores, including VSAM, DB2 (static SQL), IMS, and others.
The gateway can access any application capable of using the CPI-C API either directly or through a TP monitor such as CICS.
1.2 Features of the Gateway
The Oracle Database Gateway for APPC provides the following benefits:
TCP/IP support for IMS Connect
This release of the gateway includes TCP/IP support for IMS Connect, providing users a choice between the SNA or TCP/IP communication protocol. IMS Connect is an IBM product which enables TCP/IP clients to trigger execution of IMS transactions. The gateway can use a TCP/IP communication protocol to access IMS Connect, which triggers execution of IMS transactions. If you choose to use TCP/IP, then there is no SNA involvement with this configuration.
The gateway is optimized for minimum network traffic when you execute programs remotely. The interface to the gateway is an optimized PL/SQL stored procedure specification called the transaction interface package (TIP). This specification is precompiled in the Oracle database. Because there are no additional software layers on the remote host system, overhead occurs only when your program executes.
Platform independence
Client applications need not be operating system-specific. For example, your application can call a program on a CICS Transaction Server for z/OS. If you move the program to a CICS region on pSeries, then you need not change the application.
Application transparency
Users calling applications that execute a remote transaction program are unaware that a request is sent to a host.
Flexible interface
You can use the gateway as an interface with an existing procedural logic or to integrate new procedural logic into an Oracle database environment.
Oracle database integration
Integration of Oracle database with the gateway enables you to benefit from existing and future Oracle features. For example, the gateway can be called from an Oracle stored procedure or database trigger.
Transactional support
The gateway and the Oracle database allow remote transaction updates and Oracle database updates to be performed in a coordinated fashion.
Wide selection of tools
The gateway supports any tool or application that supports PL/SQL.
PL/SQL code generator
The Oracle Database Gateway for APPC provides a powerful development environment, including:
A data dictionary to store information relevant to the remote transaction
A tool to generate the PL/SQL Transaction Interface Package, or TIP
A report utility to view the information stored in the gateway dictionary
A complete set of tracing and debugging facilities
A wide set of samples to demonstrate the use of the product against datastores such as DB2, IMS, and CICS.
Site autonomy and security
The gateway provides site autonomy, allowing you to perform tasks such as authenticate users. It also provides role-based security compatible with any security package running on your mainframe computer.
Automatic conversion
Through TIP, the following conversions are performed:
ASCII to and from EBCDIC
Remote transaction program data types to and from PL/SQL data types
National language support for many languages
1.3 Terms
The following terms and definitions are used throughout this guide. Refer to Appendix C, "Gateway Terminology" for the complete list of terms and definitions pertaining to the gateway, its components, and functions.
Oracle Database
This is any Oracle database instance that communicates with the gateway for purposes of performing remote procedural calls to execute RTP. The Oracle database can be on the same system as the gateway or on a different system. If it is on a different system, then Oracle Net is required on both systems. Refer to Figure 1-2, "Gateway Architecture" for a view of the gateway architecture.
OLTP (Online Transaction Processor)
OLTP is an online transaction processor available from other vendors, including CICS Transaction Server for z/OS, IMS/TM, and z/OS.
PGAU (Procedural Gateway Administration Utility)
PGAU is the tool that is used to define and generate PL/SQL Transaction Interface Packages (TIPs). Refer to Chapter 2, Procedural Gateway Administration Utility in the Oracle Database Gateway for APPC User's Guide for more information about PGAU.
PG DD (Data Dictionary)
This gateway component is a repository of remote host transaction (RHT) definitions and data definitions. PGAU accesses definitions in the PG DD when generating TIPs. The PG DD has data type dependencies because it supports the PGAU and is not intended to be directly accessed by the customer. Refer to Appendix A, Procedural Gateway for APPC Data Dictionary in the Oracle Database Gateway for APPC User's Guide for a list of PG DD tables.
A remote transaction program is a customer-written transaction, running under the control of an OLTP, which the user invokes remotely using a PL/SQL procedure. To execute a remote transaction program through the gateway, you must use RPC to execute a PL/SQL program to call the gateway functions.
TIP (Transaction Interface Package)
A TIP is an Oracle PL/SQL package that exists between your application and the remote transaction program. TIP is a set of PL/SQL stored procedures that invoke the remote transaction program through the gateway. TIPs perform the conversion and reformatting of remote host data using PL/SQL and UTL_RAW/UTL_PG functions.
Figure 1-1 illustrates the Relationship of the gateway and the Oracle database. The terminology discussed in the preceding sections has been used in the architecture of the gateway.
Figure 1-1 Relationship of Gateway and the Oracle Database
The architecture of Oracle Database Gateway for APPC consists of several components:
Oracle database
The gateway
Oracle Database Gateway for APPC must be installed on a server that can run the required version of the operating system.
An OLTP (online transaction processor)
The OLTP must be accessible from the gateway using SNA or TCP/IP communication protocol. Multiple Oracle databases can access the same gateway. A single system gateway installation can be configured to access more than one OLTP.
Note:
For a gateway using TCP/IP support for IMS Connect the only OLTP that is supported through TCP/IP is IMS through IMS Connect
The OLTP must be accessible to the system using the TCP/IP protocol. Multiple Oracle databases can access the same gateway. A single system gateway installation can be configured to access more than one OLTP. Multiple IMS can be accessed from an IMS Connect. If you have a number of IMS Connect systems available, any of these may be connected to one or more IMS systems.
Figure 1-2 illustrates the architecture of Oracle Database Gateway for APPC using either SNA or TCP/IP, as described in the preceding section.
The basic structure of the gateway is the same whether your communications protocol is SNA or TCP/IP support for IMS Connect. The gateway has some of the same components as an Oracle database instance on UNIX. It has the following components:
A home directory, similar to the one associated with an Oracle instance ORACLE_HOME environment variable
A system identifier, identified as sid or ORACLE_SID
An initialization parameter file, similar to the Oracle database initsid.ora file.
The gateway does not have:
Control, redo log, or database files
The full set of subdirectories and ancillary files associated with an installed Oracle database
Because the gateway has no background processes and does not need a management utility such as Oracle Enterprise Manager, you do not need to start the gateway. Each Oracle database user session that accesses a particular gateway creates an independent process on UNIX which in turn runs the gateway server and executes either the SNA or TCP/IP functions to communicate with an OLTP.
1.6 Communication With the Gateway
All communication between the user or client program and the gateway is handled through a transaction interface package (TIP), which executes on an Oracle database. The TIP is a standard PL/SQL package that provides the following functions:
Declares the PL/SQL variables that can be exchanged with a remote transaction program
Calls the gateway packages that handle the communications for starting the conversation, exchanging data and terminating the conversation
Handles all data type conversions between PL/SQL data types and the target program data types
The Procedural Gateway Administration Utility (PGAU), provided with the gateway automatically generates the TIP specification.
The gateway is identified to the Oracle database using a database link. The database link is the same construct used to identify other Oracle databases. The functions in the gateway are referenced in PL/SQL as:
function_name@dblink_name
1.7 RPC Functions
The Oracle Database Gateway for APPC provides a set of functions that are invoked by the client through RPC. These functions direct the gateway to initiate, transfer data, and terminate remote transaction programs running under an OLTP on another system.
Table 1-1 lists the remote procedural call functions and the correlating commands that are invoked in the gateway and remote host.
Table 1-1 RPC Functions and Commands in the Gateway and Remote Host
Applications
Oracle TIP
Gateway
Remote Host
call tip_init
tip_init
call pgainit@gateway
PGAINIT
Initiate program
call tip_main
tip_main
call pgaxfer@gateway
PGAXFER
Exchange data
call tip_term
tip_term
call pgaterm@gateway
PGATERM
Terminate program
1.7.1 Description of RPC Functions
The following sections describe how the RPC functions perform on gateways using SNA or TCP/IP communication protocols.
1.7.1.1 Remote Transaction Initiation
The TIP initiates a connection to the remote host system, using one of the gateway functions, PGAINIT.
When the communication protocol is SNA: PGAINIT provides, as input, the required SNA parameters to start a conversation with the target transaction program. These parameters are sent across the SNA network, which returns a conversation identifier to PGAINIT. Any future calls to the target program use the conversation identifier as an INPUT parameter.
When the communication protocol is TCP/IP: PGAINIT provides, as input, the required TCP/IP parameters. Use the pg4tcpmap tool to map the parameters. These parameters are sent across the TCP/IP network to start the conversation with the target transaction program. The TCP/IP network returns a socket file descriptor to PGAINIT. Any future calls to the target program made by PGAXFER and PGATERM use the socket file descriptor as an input parameter.
After the conversation is established, a database gateway function called PGAXFER can exchange data in the form of input and output variables. PGAXFER sends and receives buffers to and from the target transaction program. The gateway sees a buffer as only a RAW stream of bytes. The TIP that is residing in the Oracle database is responsible for converting the application PL/SQL data types to RAW before sending the buffer to the gateway. It is also responsible for converting RAW to the PL/SQL data types before returning the results to the application.
1.7.1.3 Remote Transaction Termination
When communication with the remote program is complete, the gateway function PGATERM terminates the conversation between the gateway and the remote host.
When the communication protocol is SNA, PGATERM uses the conversation identifier as an INPUT parameter to request conversation termination.
When the communication protocol is TCP/IP, PGATERM uses the socket file descriptor for TCP/IP as an INPUT parameter to request conversation termination.
1.8 Transaction Types for Gateway Using SNA
The Oracle Database Gateway for APPC supports three types of transactions that read data from and write data to remote host systems:
One-shot
In a one-shot transaction, the application initializes the connection, exchanges data and terminates the connection, all in a single call.
Persistent
In a persistent transaction, multiple calls to exchange data with the remote transaction can be made before terminating the conversation.
Multiconversational
In a multiconversation transaction, the database gateway server can be used to exchange multiple records in one call to the remote transaction program.
You can initiate an IMS/TM transaction that executes static SQL in DB2; this illustrates the power of the Oracle Database Gateway for APPC feature supporting TCP/IP for IMS Connect.
PK v v PK >A
OEBPS/ch4.htmXp
Installing the Gateway
4 Installing the Gateway
This chapter describes how to install and configure the Oracle Database Gateway for APPC. It contains the following sections:
Configuring an online transaction processor to allow access by the gateway requires actions on the OLTP and on certain components of the host operating system. Although no Oracle software is installed on the host system, access to, and some knowledge of the host system and the OLTP are required. Although this chapter includes some information about host system and OLTP installation steps, you must ensure that you have the applicable OLTP and host system documentation available.
Some configuration actions on the OLTP might require you to restart the OLTP. Ensure that your host system programmer or DBA review the instructions for your OLTP before you restart it.
To install and configure the gateway with a single Oracle database and a single OLTP, perform the procedures described in this chapter.
This section is only for customers who have a previous release of Oracle Database Gateway for APPC. If you have a previous gateway installation, then you need to perform some tasks before you can install release 11.2 of the Oracle Database Gateway for APPC.
Note:
After reading this section, you must read Chapter 14, "Migration From Existing Gateways" to determine the specific actions you must perform to prepare for upgrade or migration of your gateway. If you are migrating to Oracle Database Gateway for APPC release 11.2 from version 4.01 or earlier, then you will find content related to migrating the gateway in Chapter 14, "Migration From Existing Gateways".
If you are installing Oracle Database Gateway for APPC for the first time, then begin with "Preinstallation Steps".
Perform the following steps to prepare for upgrading the previous versions of Oracle Database Gateway for APPC to current versions:
Make backups of altered PGA shipped files.
Remove or rename any old gateway directories.
4.2.2Upgrade and Migration Considerations
Upgrade considerations are as follows:
PGAU control files from Gateway release 8 or 9 are upward compatible and you do not need to change them.
After upgrade, the PG Data Dictionary (PG DD) contains all of its earlier entries without modification. New PGAU control information is added along with some columns to support new features, but no customer entries are altered by the upgrade.
All TIPs from Oracle Database Gateway for APPC release 4.0.1 or earlier must be recompiled because of the changes in the following:
PL/SQL compatibility
Gateway server RPC interface
UTL_PG interface
If you have existing TIPs that were generated previously on a gateway using the SNA communication protocol and you want to utilize the new TCP/IP feature, then TIPs will have to be regenerated by PGAU with mandatory NLS_LANGUAGE and Side Profile Settings. Specify the appropriate ASCII character set in the DEFINE TRANSACTION command.
This is because the gateway assumes that the user exit in IMS Connect is being used, which would translate between the ASCII and EBCDIC character sets.
Caution:
An upgraded PG Data Dictionary (PG DD) cannot be accessed by an earlier release of PGAU.
4.2.3 Restoration
If you want to restore a previous release of gateway, then you must restore the following components to their previous versions:
PGAU
PG DD
Gateway server
4.3 Preinstallation Steps
Before you install the gateway, perform the following pre-installation procedures:
Refer to Chapter 3, "System Requirements" for more information about the security requirements for connections and data access on your OLTP.
Fill out the worksheet identifying unique parameter names needed to configure your system and your chosen communication protocol (either SNA or TCP/IP), which is located in Appendix D, "Configuration Worksheet".
Decide on a SID (system identifier) for your gateway. This SID is used in "Configuring the Gateway".
The SID must be unique and must not be used by any other gateway or Oracle database on the system.
SNA only: Your SNA package must be installed and configured before you can proceed with installation of the gateway. Ensure that your system can communicate with the OLTP using the SNA communication package appropriate for your platform.
For more information about setting up and configuring the SNA communication package your platform needs to run the Oracle Database Gateway for APPC, refer to the appropriate chapter in this guide from the following list:
TCP/IP only: Your TCP/IP package must be installed and configured before you can proceed with installation of the gateway.
Ensure that your system can communicate with the OLTP using the TCP/IP communication package for your platform.
If you need general information about installing Oracle products and using the Oracle Universal Installer, then refer to the Oracle Database Installation Guide.
4.3.1 Gateway Installation Methods
You can install the gateway in any of the following ways:
On the same system as the existing Oracle database but in a different directory.
All tasks for this type of installation or upgrade are discussed in this section.
On a system different from a local Oracle database.
On the same system as the Oracle database, and in the same Oracle home directory. Note that in this case, the Oracle database and the gateway must be at the same Release level.
4.4 Installing the Gateway Software
For general information about installing Oracle products and how to use the Oracle Universal Installer, refer to the Oracle Database Installation Guide and perform all necessary tasks there first.
If your server release is different than your gateway release, do not install the gateway in the same Oracle home directory as the Oracle database. This is required to isolate the gateway from the Oracle database upgrades that might cause incompatibilities if the gateway executables were relinked with later versions of the Oracle database libraries.
4.5 Installation Steps
If you want to install the gateway in the same Oracle home as the Oracle database, then the release number of both products must be the same. This section provides the steps for installing the gateway. It contains the following topics:
4.5.1 Step through the Oracle Universal Installer
Caution:
Oracle Universal Installer automatically installs the Oracle-supplied version of the Java Runtime Environment (JRE). This version is required to run the Oracle Universal Installer and several Oracle assistants. Do not modify the JRE except by using a patch provided by Oracle Support Services. The Oracle Universal Installer also installs JDK.
Oracle Universal Installer is a menu-driven utility that guides you through installing the gateway by prompting you with action items. The action items and the sequence in which they appear depend on your platform.
The following section describes how use the Oracle Universal Installer to install the gateway on your platform:
4.5.1.1 Oracle Universal Installer on UNIX platforms
Use Table 4-1 as a guide to step through the Oracle Universal Installer. At each prompt from the Oracle Universal Installer, perform the actions described in the Response column of the table to install the gateway on your UNIX platform.
Table 4-1 The Oracle Universal Installer: Steps for Installing the Gateway
Prompt
Response
Oracle Universal Installer: Welcome
Click Next.
Oracle Universal Installer: Specify Inventory Directory and credentials
a. Specify the full path of the inventory directory.
b. Specify the operating system group name.
c. Click Next.
Oracle Universal Installer: Specify Home Details
a. Specify the name of the installation.
b. Specify the full path where you want to install the product.
c. Click Next.
Oracle Universal Installer: Available Product Components
a. Deselect the checked products.
b. Select "Oracle Database Gateway 11.2", open up this row.
c. Select "Oracle Database Gateway for APPC 11.2".
d. Click Next.
Oracle Universal Installer: Network Software
Specify your network package and click Next.
Oracle Universal Installer: Summary
Click Install.
Oracle Net Configuration Assistance: Welcome
Click Next.
Oracle Net Configuration Assistance: Listener Configuration, Listener Name
Specify the name of Listener you want to create and click Next.
Oracle Net Configuration Assistance: Listener Configuration, Select Protocols
Select the protocols and click Next.
Oracle Net Configuration Assistance: Listener Configuration, TCP/IP Protocol
Specify a port number and click Next.
Oracle Net Configuration Assistance:Listener Configuration, More Listeners?
Click "No" and then click Next.
Oracle Net Configuration Assistance: Listener Configuration Done
Click Next.
Oracle net Configuration Assistance: Naming Methods Configuration
Click No and then click Next.
Oracle Net Configuration Assistance: Done
Click Finish.
Execute Configuration scripts
You must run the root.sh configuration script from the $ORACLE_HOME directory at this point. Leave the installation open, run the script as the root user from another window, then come back to the installation screen and click OK to continue.
Oracle Universal Installer: End of Installation
Click Exit.
When the Oracle Universal Installer confirms that the installation is complete, verify that the installation procedure was successful. To do this, read the contents of the installation log file, which is located in the $ORACLE_HOME/install directory. The default file name is make.log.
Attention:
Print the contents of the $ORACLE_HOME/dg4appc/doc/README.doc file and read the entire document; it contains important information about the installation. After reading the README.doc file, proceed with configuration of the gateway.
4.6 Deinstalling Oracle Database Gateway for APPC
This section describes how to remove Oracle Database Gateway from an Oracle home directory. It contains information about the following topics:
The Deinstallation Tool (deinstall) is available in the installation media before installation, and is available in Oracle home directories after installation. It is located in the path $ORACLE_HOME/deinstall.
The deinstall command stops Oracle software, and removes Oracle software and configuration files on the operating system.
The command uses the following syntax, where variable content is indicated by italics:
deinstall -home complete path of Oracle home [-silent] [-checkonly] [-local]
[-paramfile complete path of input parameter property file] [-params name1=value
name2=value . . .] [-o complete path of directory for saving files] [-help | -h]
The options are:
-silent
Use this flag to run the command in silent or response file mode. If you use the -silent flag, then you must use the -paramfile flag, and provide a parameter file that contains the configuration values for the Oracle home that you want to deinstall or deconfigure.
You can generate a parameter file to use or modify by running deinstall with the -checkonly flag. The deinstall command then discovers information from the Oracle home that you want to deinstall and deconfigure. It generates the properties file, which you can then use with the -silent option.
You can also modify the template file deinstall.rsp.tmpl, located in the response folder.
-checkonly
Use this flag to check the status of the Oracle software home configuration. Running the command with the -checkonly flag does not remove the Oracle configuration. The -checkonly flag generates a parameter file that you can use with the deinstall command.
-local
Use this flag on a multinode environment to deconfigure Oracle software in a cluster.
When you run deconfig with this flag, it deconfigures and deinstalls the Oracle software on the local node (the node where deconfig is run). On remote nodes, it deconfigures Oracle software, but does not deinstall the Oracle software.
-paramfilecomplete path of input parameter property file
Use this flag to run deconfig with a parameter file in a location other than the default. When you use this flag, provide the complete path where the parameter file is located.
The default location of the parameter file depends on the location of deconfig:
From the installation media or stage location: $ORACLE_HOME/inventory/response
From a unzipped archive file from OTN: /ziplocation/response
After installation from the installed Oracle home: $ORACLE_HOME/deinstall/response
Use this flag with a parameter file to override one or more values that you want to change in a parameter file you have already created.
-ocomplete path of directory for saving response files
Use this flag to provide a path other than the default location where the properties file (deinstall.rsp.tmpl) is saved.
The default location of the parameter file depends on the location of deconfig:
From the installation media or stage location before installation: $ORACLE_HOME/
From a unzipped archive file from OTN: /ziplocation/response/
After installation from the installed Oracle home: $ORACLE_HOME/deinstall/response
-help | -h
Use the help option (-help or -h) to obtain additional information about the command option flags.
4.6.2 Removing Oracle Software
Complete the following procedure to remove Oracle software:
Log in as the installation owner.
Run the deinstall command, providing information about your servers as prompted.
PK& ]p Xp PK >A
OEBPS/ch6.htmI
Configuring the SNA Communication Package on Linux
6 Configuring the SNA Communication Package on Linux
The Oracle Database Gateway for APPC uses the SNA Advanced Program to Program Communication (APPC/LU6.2) protocol to communicate with an OLTP. Linux for Intel Pentium-based 32-bit system support for APPC is provided by IBM Communications Server for Linux.
This chapter describes how to configure your SNA Server on a Linux for Intel Pentium-based 32-bit system to run the Oracle Database Gateway for APPC, using IBM Communications Server for Linux.
The term SNA Server is used in this guide to generally refer to the IBM Communications Server.
6.1 Using SNA Security Validation
When the gateway receives an RPC request to start a remote transaction program, the gateway attempts to start an APPC conversation with online transaction processing (OLTP). Before the conversation can begin, a session must start between the Linux Logical Unit (LU) and the OLTP LU.
SNA and its various access method implementations (including SNA Server and VTAM) provide security validation at session initiation time, enabling each LU to authenticate its partner. This validation is carried out entirely by network software before the gateway and OLTP application programs begin their conversation and process conversation-level security data. If session-level security is used, then correct password information must be established in the gateway SNA Server definitions and in similar parameter structures in the OLTP to be accessed. Refer to the appropriate communications software product documentation for detailed information about this subject.
6.2 Processing Inbound Connections
Many OLTPs provide options for manipulating the security conduct of an inbound (client) APPC session request. Refer to the appropriate OLTP documentation for detailed information about this topic.
Note:
For CICS, one security option is not supported by the gateway: ATTACHSEC=PERSISTENT, specified in the CICS CONNECTION definition, requires capability that is not yet available in the gateway.
However, the ATTACHSEC=LOCAL, ATTACHSEC=IDENTIFY, ATTACHSEC=VERIFY, and ATTACHSEC=MIXIDPE security options are fully supported by the gateway.
6.3 Independent Versus Dependent LUs
Oracle recommends that you use independent LUs for the Oracle Database Gateway for APPC because they support multiple parallel sessions or conversations. This means that multiple Oracle client applications can be active simultaneously using the same OLTP through the independent LU.
Dependent LUs support only a single active session. The CP (Control Point for the node) queues additional conversation requests from the gateway server behind an already active conversation.In other words, conversations are single threaded for dependent LUs. If a gateway LU is correctly defined, then you do not need to alter the configuration for the Oracle Database Gateway for APPC and the gateway server.
The operational impact of dependent LUs is that the first client application can initiate a conversation through the Oracle Database Gateway with the gateway server. While that transaction is active (which could be seconds to minutes to hours, depending on how the client application and transaction are designed), any other client application initiating a session with the same gateway server appears to hang as it waits behind the previous session.
If a production application uses only a single conversation at any one time, then there should be no impact.
However, additional concurrent conversations might be required for testing or for other application development. Each conversation requires that you define additional dependent LUs on the remote host, plus additional IBM Communication Server configuration entries, which define the additional dependent LUs on the gateway system. Additional Side Information Profiles should be defined to use the new dependent LUs. New gateway instances should be created and configured to use these new Side Information Profiles.
Several types of IBM Communications Server definitions are relevant to gateway APPC/LU6.2 operation. Each definition can be created and edited using a corresponding SNA Node Configuration menu.The definitions relevant to the gateway are presented in Section 6.5 in hierarchical order. This section provides an overview of IBM Communications Server definitions in relation to the Oracle Database Gateway for APPC. Those definition types that are lowest in the hierarchy are discussed first. This matches the logical sequence in which to create the definitions.Refer to the IBM Communications Server online documentation for a complete discussion of IBM Communications Server definitions.
6.5 Creating IBM Communications Server Definitions for the Gateway
IBM Communications Server definitions are created using the SNA Node Configuration tool, while the operation of the server is done using the SNA Node Operations tool, both of which are provided with IBM Communications Server. Maintenance of SNA definitions is normally done by a user with Administrator privileges.
The following sections describe the process of creating SNA definitions for IBM Communications Server using the SNA Node Configuration tool. All of the tasks described in this section are performed within SNA Node Configuration.
The SNA Node Configuration screen prompts you to specify if you are creating a new configuration or loading an existing configuration. These tasks are based on the assumption that a new configuration is being created.
SNA Node Configuration next prompts you for a configuration scenario.
6.5.2 Creating the Node
Each SNA Server must have a Control Point defined. This is typically called the Node definition. To define the node:
Click Node.
Click Create.
In the Define the Node dialog box:
Select the Basic tab.
Enter information in the Control Point, Local Node ID, and Node Type boxes.
You can select Advanced tab options depending on your SNA network configuration.
Click OK.
6.5.3 Creating Devices
To configure communication devices:
Click Devices.
Click Create.
6.5.4 Choosing the Device Type
Select the type of device to use for communication. The LAN type is typical for either Ethernet or Token Ring attached network devices.
6.5.5 Configuring a LAN Device
To configure a LAN device:
Select the Basic tab.
Choose the Adapter to use and the Local SAP. The other tabs provide options for network tuning parameters.
Click OK.
6.5.6 Creating Peer Connections
To create peer connections:
Click Peer Connections.
Click Create.
6.5.7 Defining the Link Station
To define the link station:
In the Basic tab, enter a Link Station name for this connection.
Choose the device for the connection.
Enter the Destination address and Remote SAP.
6.5.8 Defining the Adjacent Node
To define the adjacent node:
Select the Adjacent Node tab.
Enter the Adjacent CP name of the remote system and select its CP type.
You might have to choose a different transmission group (TG) than the default. Consult your SNA network administrator for details.Other tabs provide options on tuning and reactivation.
Click OK.
6.5.9 Creating Local LUs
To create local LUs for the node:
Click Local LU 6.2 LUs.
Click Create.
6.5.10 Defining Local LUs
To define local LUs:
In the Basic tab, enter the name of the Local LU, and, optionally, an alias. The name must match the Local LU definition of the remote host for this Node. You can examine the other tab for synchronization support and for LU session limits.
Click OK.
6.5.11 Creating Partner LUs
To create partner LUs:
Click Partner LU 6.2 LUs.
Click Create.
6.5.12 Defining Partner LUs
To define partner LUs:
In the Basic tab, enter the name of the Remote or Partner LU, and, optionally, an alias.
Choose the Fully Qualified CP from the Existing list. You can examine the other tab for logical record limits and security support.
Click OK.
6.5.13 Creating the CPI-C Side Information Profile
To define the CPI-C profile that will be used to create the gateway:
Click the CPI-C Side Information Definitions.
Click Create.
6.6 Testing the Connection
Before proceeding with the gateway configuration tasks, ensure that your connection is working.
Figure 6-1 shows the relationship between SNA Server definitions and the VTAM definitions on the host.
When you have finished configuring the SNA communication package for your Linux for Intel Pentium-based 32-bit System, proceed to Chapter 10, "Configuring the OLTP" to continue configuring the network.
PKK}I I PK >A
OEBPS/apb.htmx<
Gateway Initialization Parameters for TCP/IP Communication Protocol
B Gateway Initialization Parameters for TCP/IP Communication Protocol
This appendix describes the parameters needed for a gateway featuring the TCP/IP for IMS Connect communication protocol. It also provides a sample output of the pg4tcpmap tool. In addition, this appendix contains sample listener.ora and tnsnames.ora files for a gateway using TCP/IP. It contains the following sections:
B.1 Gateway Initialization Parameter File Using TCP/IP
The parameter file for the Oracle Database Gateway for APPC using TCP/IP for IMS Connect is located in the $ORACLE_HOME/dg4appc/admin directory and is called initsid.ora.
Note:
The initsid.ora file contains both SNA and TCP/IP parameters. You will need to modify these files with the suitable parameters.
B.1.1 PGA Parameters
The PGA parameters control the TCP/IP interface portion of the gateway. PGA parameters are specified using the SETgateway initialization parameter. For example:
SET pga_parm=value
where:
pga_parm is one of the PGA parameter names in the list that follows
value is a character string with contents that depend on pga_parm
Table B-1 provides a list of PGA parameters and their descriptions.
Table B-1 PGA Parameters on Gateway Using TCP/IP for IMS Connect
Parameter
Description
LOG_DESTINATION=logpath
logpath specifies the destination at which STDERR is reopened. LOG_DESTINATION specifies a directory only and STDERR is reopened to logpath/sid_pid.log
where:
sid is the sid name
pid is the process ID assigned to the gateway
NOTE: This parameter will be used for the pg4tcpmap tool when you set the Trace Level to 255. The log file for this tool will reside in the same place as the gateway log file, in pg4tcpmap_sid.log.
PGA_CAPABILITY
PGA transaction capability. The following are valid values:
READ_ONLY or RO: Read-only capabilities.
SINGLE_SITE or SS: Single-site update only. This indicates that in a distributed environment, only the gateway can perform updates. No other database updates can occur within the Oracle transaction.
The default is SINGLE_SITE.
PGA_SECURITY_TYPE
TCP/IP conversation security option. This controls what security parameters are sent to the OLTP. The following are valid values:
Important: You must specify your RACF group name through the pg4tcpmap tool if you have set your PGA security option to SECURITY=PROGRAM. For more information about this issue, refer to the Oracle Database Gateway for APPC User's Guide.
If you have already loaded the table pga_tcp_imsc and you did not first specify the RACF group name, delete the row and reinsert it with the value for the RACF group name.
PGA_TCP_DB
The Oracle Net service name for the Oracle database in which the gateway receives its TCP/IP for IMS Connect information, such as host name and port number. This parameter can be from 1 to 255 characters long. This parameter is required.
There is no default value.
PGA_TCP_PASS
The Oracle password to be used by the gateway when connecting to the Oracle database specified by the PGA_TCP_DB parameter. The password can be from 1 to 30 characters long. This parameter is required. The password can be encrypted. For more information about encrypting the password, refer to Passwords in the Gateway Initialization File.
There is no default value.
PGA_TCP_USER
The Oracle user ID to be used by the gateway when connecting to the Oracle database specified by the PGA_TCP_DB parameter. The user ID can be from 1 to 30 characters long. This parameter is required.
There is no default value.
TRACE_LEVEL
PGA trace level. This controls tracing output written to STDERR (the target of the LOG_DESTINATION parameter). The value must be an integer from 0 to 255.
The default is 0, indicating no tracing.
NOTE: This parameter is used in the pg4tcpmap tool as well as the gateway.
Note that input in this sample is shown within angle brackets (<>).
$ pg4tcpmap
PG4TCPMAP: Release 11.2.0.1.0 - Production on Thu Jun 11 15:09:00 2009
This tool takes the IMS Connect TCP/IP information, such as host name
and port number and maps them to your TIPs.
You may use this tool to insert or delete IMS Connect TCP/IP information.
If you want to insert a row, type I
If you want to delete a row, type D
i
Enter the Unique Side Profile.
IMSPGA
Enter either the remote hostname or its TCP/IP address.
mvs09
Enter the IMS CONNECT port number.
9900
Do you want to select a CONVERSATIONAL PROTOCOL?(Y|N)
The default is NO, 'no request for acknowledgment or deallocation'
n
Enter one of the following letters for Timer.
For .25 second, enter 'D'.
For .01 to .25 second, enter 'S'.
For 'does not set the timer, no wait occurs', enter 'N'.
For Receive waits indefinitely, enter 'I'.
The default is 'D'.
D
Enter one of the following letters for 'socket connection type'.
For transaction socket, enter 'T'.
For persistent socket, enter 'P'.
For non-persistent socket, enter 'N'.
The default is 'T'.
T
Do you want to enter the CLIENT ID name? (Y|N)
If NO, IMS CONNECT (USER EXIT) will generate it.
n
Enter one of the following letters for 'COMMIT MODE'.
For Commit Mode set to 0, enter '0'.
For Commit Mode set to 1, enter '1'.
The default is '1'.
1
Enter the DATASTORE name (IMS DESTINATION ID).
The maximum string length is 8 and the Datastore name must be specified.
IMSE
Do you want to enter the LTERM? (Y|N)
If NO, the default is blank.
n
Do you want to enter the RACF GROUP name? (Y|N)
If NO, the default is blank.
n
Do you want to enter the IRM_ID? (Y|N)
If NO, the default is *IRMREQ*.
n
Does your exit return the LLLL prefix field? (Y|N)
The default is 'N'.
n
Requested to INSERT a row.
'Side Profile name' is 'IMSPGA'
'remote host name' is 'MVS09'
'IMS Connect port number' is '9900'
'conversational protocol' is ' '
'Timer' is 'D'
'socket connection type' is 'T'
'client ID' is ' '
'commit mode' is '1'
'Datastore name (IMS destination ID)' is 'IMSE '
'IMS LTERM override' is ' '
'RACF group name' is ' '
'IRM ID' is '*IRMREQ*'
'LLLL prefix present' is 'N'
PG4TCPMAP is complete.
B.2.1 Sample listener.ora File for a Gateway Using TCP/IP
The following is an example of a listener.ora file for a gateway using TCP/IP:
The Oracle Database Gateway for APPC provides Oracle applications with seamless access to IBM mainframe data and services through Remote Procedure Call (RPC) processing.
The UNIX platforms supported by this gateway release are:
AIX 5L Based Systems (64-Bit)
HP-UX Itanium
Solaris Operating System (SPARC 64-Bit)
Linux x86
Linux x86-64
Refer to the Oracle Database Installation Guide and to the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at
Read this guide if you are responsible for tasks such as:
Determining hardware and software requirements.
Installing, configuring, or administering an Oracle Database Gateway for APPC.
Developing applications that access remote host databases through the gateway using either the SNA communication protocol or the TCP/IP for IMS Connect communication protocol.
Determining security requirements.
Determining and resolving problems.
Before using this guide to administer the gateway, you should understand the fundamentals of the operating system for your platform and Oracle Database Gateways.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
Related Documents
The Oracle Database Gateway for APPC Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64 is included as part of your product shipment. Also included is:
You might also need Oracle database and Oracle Net documentation. The following is a useful list of the Oracle publications that might be referenced in this guide:
In addition to your Oracle documentation, ensure that you have appropriate documentation for your platform, for your operating system and for your communications packages. You may find IMS Connect Guide and Reference IBM documentation useful.
Note:
For other Operating System and SNA communication package and TCP/IP package references, refer to the appropriate vendor documentation for your system
Conventions
The following text conventions are used in this document:
Convention
Meaning
boldface
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
Command Syntax
UNIX command syntax appears in monospace font. The dollar character ($), number sign (#), or percent character (%) are UNIX command prompts. Do not enter them as part of the command. The following command syntax conventions are used in this guide:
Convention
Description
backslash \
A backslash is the UNIX command continuation character. It is used in command examples that are too long to fit on a single line. Enter the command as displayed (with a backslash) or enter it on a single line without a backslash:
The Gateway Password Encryption tool (tg4pwd) has been replaced by a generic feature that is now part of Heterogeneous Services. Refer to Chapter 15, "Security Considerations" in Oracle Database Gateway Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64 or Oracle Database Gateway Installation and Configuration Guide for Microsoft Windows for details.
2.2.2 Partial IPv6 Support
There is full IPv6 support between Oracle databases and the gateway but IPv6 is not yet supported between the gateway and IMS Connect.
2.3 Known Restrictions
The following sections list the known restrictions for the Oracle Database Gateway for APPC and PGAU.
The following restrictions are known to exist in this release of the Oracle Database Gateway for APPC.
Multibyte Character Sets are Not Supported for Numeric Data and Clauses
The Oracle Database Gateway for APPC has supported multibyte character set data for COBOL PIC G data types from version 3.4 onwards. However, the non-numeric character data (such as $, (,), +, -,.) that is allowed in DISPLAY data types and PIC 9 edit masks must still be specified in EBCDIC. The non-numeric character data is not subject to MBCS translation.
CICS Transactions Do Not Allow PF Key Emulation
When performing a CICS transaction using the Oracle Database Gateway for APPC, you cannot emulate CICS PF keys.
APPC PIP Data is Not Supported
You cannot define and transmit APPC PIP data in this release of the Oracle Database Gateway for APPC.
Floating Point Datatype Conversion is Not Supported
Conversion of the floating point data type is not supported by the Oracle Database Gateway for APPC.
Transaction Programs are Responsible for All Data Compression and Decompression
The Oracle Database Gateway for APPC does not provide exits for compression and decompression facilities. All data exchanged between the gateway and the transaction must be in uncompressed format.
IBM VS COBOL II Compiler Desupported
The IBM VS COBOL II compiler has been desupported. However, the string "IBMVSCOBOLII" is still used as the value of the compiler name parameter to represent any COBOL compiler you choose to use. The value IBMVSCOBOLII should still be used and does not create a dependency on any specific version of the compiler.
2.3.2Known Restrictions for PGAU
When COBOL input to the PGAU DEFINE DATA statement contains a COPY REPLACE clause, only the first replacement is made.
PK_. PK >A OEBPS/ch15.htmuH
Migration From Existing Gateways
14 Migration From Existing Gateways
Migrating to new instances of Oracle Database Gateway for APPC from an existing installation is straightforward, provided you follow some guidelines. This chapter provides information to make these new installations as easy as possible. It also provides the parameters you need if you are using the TCP/IP for IMS Connect communication protocol on your gateway.
This chapter provides information that is specific to this release of Oracle Database Gateway for APPC for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64. It contains the following sections:
14.1 Migrating An Existing Gateway Instance to a New Release Using SNA Protocol
Follow these steps to migrate an existing gateway to Release 11.2 of the gateway using the SNA communication protocol.
Note that if you are using the gateway TCP/IP support for IMS Connect, you will not be migrating an existing release to the current release of the gateway. However, you will need to place valid Heterogeneous Services parameters into your initsid.ora file. Proceed to "Parameter Changes: Version 4 to Release 11.2 of the Gateway".
Do not install the gateway over a previously existing gateway installation. Doing this corrupts the existing installation.
14.1.2 Step 2: Transferring the initsid.ora Gateway Initialization File Parameters
Copy the initsid.ora file from the old gateway instance to the new instance.
If you are migrating from Release 9.0.1 or earlier of the gateway, PGA_TRACE is not supported. You need to modify the parameter to TRACE_LEVEL instead.
Note:
If you are using TRACE_LEVEL, you must set the path for the LOG_DESTINATION parameter.
If you have encrypted some of the parameters at file initsid.ora by using dg4pwd, copy the $ORACLE_HOMRE/dg4appc/admin/initsid.pwd file from the old gateway instance to the new instance.
Note:
If you are migrating from Release 9.0.1 or earlier of the gateway, you do not need to copy this file into the new instance.
14.1.3 Backout Considerations When Migrating to New Releases
Oracle recommends that you keep the old gateway Oracle home directory and instance configurations intact and operational when you are installing a new release of the gateway and upgrading existing instances, in case there are problems with the upgrade. This helps to ensure minimum down time between changes to different gateway instances.
14.1.4Oracle Net Considerations
Oracle Database Gateway for APPC uses the Heterogeneous Services (HS) facilities of Oracle and Oracle Net. If you are upgrading from a version 4 gateway, then you need to slightly modify the gateway service name entries in the tnsnames.ora file. Add an (HS=) clause to tell Oracle Net that the gateway uses HS facilities. For more information, refer to Section 5.1, "Configuring the Oracle Network for the Gateway".
14.1.5 Parameter Changes: Version 4 to Release 11.2 of the Gateway
This release of Oracle Database Gateway for APPC introduces new and changed initialization parameters if you are migrating from a Version 4 gateway to Release 11.2 of the gateway.
If you are using the gateway TCP/IP support for IMS Connect, you will not be migrating from Version 4 to the current release of the gateway. However, you need to place valid Heterogeneous Services parameters into your initsid.ora file.
This chapter contains references to the particular HS parameters that you need to run the gateway.
Following is a list of the gateway initialization file (initsid.ora) parameters that have been renamed in this release of the gateway. The former names of the parameters are shown in parentheses.
The following parameters are obsolete. If necessary, remove them from your configuration files:
MODE
SERVER_PATH
ERROR_LOGGING
ERROR_REPORTING
ERRORTAG
GATEWAY_SID
GROUP_BY_OFF
GTWDEBUG
INCREMENT_CURSORS
INIT_CURSORS
LIST
MAX_LOG_SIZE
OPTIMIZE_FILE_OPEN
ORDER_BY_OFF
RESOLVE_BINDS
RETRY
SET
SNMP_SUPPORT
SQL_TRACE
TRIM_CURSORS
D_OPEN_CURSORS
D_INIT_CURSORS
D_INCREMENT_CURSORS
D_TRIM_CURSORS
PGA_TRACE
14.1.6 Parameter Changes: Version 8 or Earlier to Gateway Release 11.2
The following startup shell script parameter must be added to initsid.ora if you are migrating from a Version 4 or Version 8 gateway to Release 11.2 of the Oracle Database Gateway for APPC:
FDS_CLASS_VERSION
14.1.7 Migrating from Gateway Release 9.0.1 or 9.2.0 or 10.1.0 to Gateway Release 11.2
No new parameters were added between release 9.0.1 and this release of the gateway.
14.2 Migrating from an Existing Gateway to TCP/IP Using SNA
The following sections are for those users who have an existing release of the gateway using the SNA protocol, but who want to switch to using TCP/IP support for IMS Connect.
The TCP/IP support for IMS Connect feature in this release of the gateway enables you to continue to use existing TIPs.
14.2.1 Using Existing TIPs with Existing Side Profile Definitions
Follow these instructions:
Make sure you have used the pg4tcpmap tool to insert valid parameter values into thePGA_TCP_IMSC table.
If your TIPs from a previous version of the gateway were already defined using a SideProfileName and the NLS_ LANGUAGE parameter has been set to a value of american_america_us7ascii, then you will not need to recompile these TIPs. You still need to map your parameter values using the pg4tcpmap tool.
Note:
TIPs must be recompiled when changing communication protocol from SNA to TCP/IP.
If you have existing TIPs that were generated previously on a gateway using the SNA communication package protocol, and you want to use the new TCP/IP feature, then the TIPs have to be regenerated by PGAU with mandatory NLS_LANGUAGE and Side Profile Settings. Specify the appropriate ASCII character set in the DEFINE TRANSACTION command.
This is because the gateway assumes that the appropriate user exit in IMS Connect is being used, which would translate between the appropriate ASCII and EBCDIC character sets.
PKIzH uH PK >A
OEBPS/apa.htm8jǕ
Gateway Initialization Parameters for SNA Protocol
A Gateway Initialization Parameters for SNA Protocol
This appendix describes the gateway initialization file location and lists the gateway initialization parameters supported by Oracle Database Gateway for APPC, specifically for the SNA protocol. These parameters are fully documented in "Migrating An Existing Gateway Instance to a New Release Using SNA Protocol". In addition, this appendix contains sample listener.ora and tnsnames files for a gateway using SNA.
The initsid.ora file contains both SNA and TCP/IP parameters. You must modify these files with suitable parameters.
A.1.1 PGA Parameters
The PGA parameters control the APPC interface portion of the gateway. PGA parameters are specified using the SETgateway initialization parameter. For example:
SET pga_parm=value
where:
pga_parm is one of the PGA parameter names in the list that follows
value is a character string with contents that depend on pga_parm
Table A-1 provides a list of PGA parameters and their descriptions.
Table A-1 PGA Parameters for Gateway Using SNA
Parameter
Description
LOG_DESTINATION=logpath
logpath specifies the destination at which STDERR is reopened. LOG_DESTINATION specifies a directory only and STDERR is reopened to logpath/sid_pid.log
where:
sid is the sid name
pid is the process ID assigned to the gateway
PGA_CAPABILITY
PGA transaction capability. This controls whether updates are allowed through the gateway. The following are valid values:
READ_ONLY or RO: Read-only capabilities.
SINGLE_SITE or SS: Single-site update only. This indicates that in a distributed environment, only the gateway can perform updates. No other database updates can occur within the Oracle transaction.
COMMIT_CONFIRM or CC: Commit-confirm. This indicates that in a distributed environment, updates can be performed by both the gateway and other participants within the Oracle transaction. The gateway is always committed first in this mode, and no other commit-confirm sites are allowed to participate in the Oracle transaction.
The default is SINGLE_SITE.
PGA_CONFIRM
Incoming APPC CONFIRM request handling option. This controls what the gateway does when an APPC CONFIRM request is received from the remote transaction program. This parameter has meaning only when the conversation is running with SYNCLEVEL set to a value higher than 0. The following are valid values:
ACCEPT - Respond to incoming APPC CONFIRM requests with APPC CONFIRMED responses.
REJECT - Treat incoming APPC CONFIRM requests as errors causing the conversation to be deallocated and an error message to be issued.
The default is REJECT.
PGA_LOG_DB
The Oracle Net service name for the Oracle database in which the gateway maintains its transaction log. This parameter can be from 1 to 255 characters long. This parameter is required only when PGA_CAPABILITY is set to COMMIT_CONFIRM.
There is no default value.
PGA_LOG_PASS
The Oracle password to be used by the gateway when connecting to the Oracle database specified by the PGA_LOG_DB parameter. The password can be from 1 to 30 characters long. This parameter is required only when PGA_CAPABILITY is set to COMMIT_CONFIRM. The password can be encrypted. For more information about encrypting the password, refer to Passwords in the Gateway Initialization File.
There is no default value.
PGA_LOG_USER
The Oracle user ID to be used by the gateway when connecting to the Oracle database specified by the PGA_LOG_DB parameter. The user ID can be from 1 to 30 characters long. This parameter is required only when PGA_CAPABILITY is set to COMMIT_CONFIRM.
There is no default value.
PGA_RECOVERY_PASS
The password to be used by the gateway when allocating an APPC conversation with the transaction specified by the PGA_RECOVERY_TPNAME parameter. The password can be from 1 to 8 characters long. This parameter is required only when PGA_CAPABILITY is set to COMMIT_CONFIRM and PGA_SECURITY_TYPE is set to PROGRAM. The password can be encrypted. For more information about encrypting the password, refer to Passwords in the Gateway Initialization File.
There is no default value.
PGA_RECOVERY_TPNAME
The TP name of the transaction installed in the OLTP for commit-confirm FORGET and RECOVERY processing. The TP name can be from 1 to 64 characters long. For CICS Transaction Server for z/OS, the TP name is limited to four characters. For IMS/TM, the TP name is limited to eight characters. Other OLTPs might have other limits on the length of the TP name. This parameter is required only when PGA_CAPABILITY is set to COMMIT_CONFIRM.
The default value is RECO.
PGA_RECOVERY_USER
The user ID to be used by the gateway when allocating an APPC conversation with the transaction specified by the PGA_RECOVERY_TPNAME parameter. The user ID can be from 1 to 8 characters long. This parameter is required only when PGA_CAPABILITY is set to COMMIT_CONFIRM and PGA_SECURITY_TYPE is set to PROGRAM or SAME.
There is no default value.
PGA_SECURITY_TYPE
APPC conversation security option. This controls what security parameters are sent to the OLTP in the FMH-5 at conversation allocation. The following are valid values:
Action to take on receipt of a SIGDANGER signal from the system indicating a shortage of paging space. The following is a valid value:
IGNORE: Ignores the signal
The default is IGNORE.
TRACE_LEVEL
PGA trace level. This controls tracing output written to STDERR (the target of the LOG_DESTINATION parameter). The value must be an integer between 0 and 255.
The default is 0, indicating no tracing.
Any value between 1 and 255 will turn tracing on.
A.1.2 PGA_CAPABILITY Parameter Considerations
When choosing a setting for the PGA_CAPABILITY parameter, take care to ensure that the correct setting is used based on what the remote transaction programs will be doing.
The READ_ONLY setting should always be used when the remote transaction programs are read-only, that is, when the remote transaction programs perform no database updates. READ_ONLY should never be used when the remote transaction programs perform database updates. For example, if the READ_ONLY setting is chosen and if a remote transaction program invoked by the gateway performs updates to a foreign database, then Oracle database does not provide any integrity protection for those updates. Furthermore, the READ_ONLY mode enables a gateway transaction to be part of a distributed transaction that might update several other databases. If the gateway invokes a remote transaction program that performs updates in this situation and if a failure occurs, then the database updated by the remote transaction program is not synchronized with the other databases.
In cases where the remote transaction programs perform updates to foreign databases, there are two options for the value of PGA_CAPABILITY:
SINGLE_SITE
COMMIT_CONFIRM
Each of these options provides protection against data integrity problems by allowing COMMIT and ROLLBACK requests to be forwarded to the remote transaction program and by informing Oracle database about the distributed update and recovery capabilities of the gateway. The particular option depends on the design of the remote transaction programs and on the capabilities of the OLTP (online transaction processor) where they execute.
If the OLTP has LU6.2 SYNCLEVEL 1 or 2 support, then the COMMIT_CONFIRM capability provides limited two-phase commit between the Oracle database and the OLTP, with the restriction that no other commit-confirm site (gateway or Oracle) can be part of the distributed transaction. If it is not possible to use COMMIT_CONFIRM, then the SINGLE_SITE capability provides update capability between Oracle database and the OLTP, with the restriction that only the OLTP can perform updates and no updates can occur on the Oracle side.
Each of the PGA_CAPABILITY options for update control imposes specific requirements on the remote transaction program and on the OLTP. For COMMIT_CONFIRM capability, these requirements are discussed in detail in Chapter 5, "Implementing Commit-Confirm," of the Oracle Database Gateway for APPC User's Guide. Also refer to Section 11.8.3, "Configuring the OLTP for Commit-Confirm" in this guide. For SINGLE_SITE capability, the remote transaction program is responsible for performing the required tasks in response to COMMIT and ROLLBACK requests received from the gateway on behalf of the Oracle database. The gateway uses the APPC CONFIRM and SEND_ERR requests to implement COMMIT and ROLLBACK, respectively. On receipt of a CONFIRM, the remote transaction program must perform COMMIT processing and then respond to the gateway with an APPC CONFIRMED response. On receipt of SEND_ERR, the remote transaction program must perform ROLLBACK processing.
Because the distributed transaction capability of the Oracle database is affected by the PGA_CAPABILITY option used by the gateway, it is desirable to separate inquiry and update applications by using different gateway instances for each. One gateway can be defined with PGA_CAPABILITY set to READ_ONLY and others with PGA_CAPABILITY set to SINGLE_SITE or COMMIT_CONFIRM.
This allows read-only transaction programs to participate in distributed transactions under the control of the Oracle database. For example, data from DB2 can be retrieved through the READ_ONLY gateway by an inquiry-only remote transaction program and can then be used as input to database updates on the Oracle database, all in one Oracle transaction. A SINGLE_SITE gateway can be used only for accessing remote transaction programs which perform updates to foreign databases outside the scope of the Oracle database control. Data can be read from any databases accessible to the Oracle database, and that data can be used to perform updates through the gateway.
When it is necessary to update resources on both the Oracle side and the OLTP side, a COMMIT_CONFIRM gateway can be used, provided that the OLTP and the remote transaction programs are set up to implement commit-confirm.
All that is necessary to set up multiple gateway instances is to set up the following for each instance:
An entry in the listener.orafile defining the sid of the gateway instance
An entry in the tnsnames.orafile defining an alias to be used to connect to the gateway instance defined in listener.ora
A database link in Oracle database that specifies the alias defined in the tnsnames.ora file in its USING parameter
Note that the gateway instances can share one common directory structure and use the same executables.
For example, to set up two gateways, PGAI and PGAU (for inquiry and update use, respectively), the following steps are required:
Define entries in listener.ora for two sids, PGAI and PGAU.
Define two aliases in tnsnames.ora that connect to the two new sids, PGAI and PGAU.
Define two database links in Oracle database, one connecting to PGAI and the other connecting to PGAU.
Finally, create the initialization files initPGAI.ora and initPGAU.ora.
In initPGAI.ora, set PGA_CAPABILITY to READ_ONLY, and in initPGAU.ora, set PGA_CAPABILITY to SINGLE_SITE or COMMIT_CONFIRM. Then, use the PGAI gateway for inquiry-only transactions, and use the PGAU gateway for update transactions.
The same steps can be used to set up additional gateway instances.
A.1.3 PGA_CONFIRM Parameter Considerations
When deciding on the setting for the PGA_CONFIRM parameter, it is important to understand the effects of each setting. First, keep in mind that this parameter affects only those conversations running at SYNCLEVEL 1. The default setting, PGA_CONFIRM=REJECT, is correct for most applications. With this setting, the gateway generates an error if a CONFIRM request is received from the remote transaction program. If you have a remote transaction that uses CONFIRM to verify that data was received by the gateway, then you must use PGA_CONFIRM=ACCEPT to allow the gateway to respond to those incoming CONFIRM requests with CONFIRMED responses. You must be aware that the gateway sends CONFIRM requests to the remote transaction when the Oracle application has sent a COMMIT request. For the COMMIT processing to work correctly, the remote transaction must be written to perform its local commit processing whenever a CONFIRM request is received from the gateway, and respond to the gateway with CONFIRMED after the commit processing has successfully completed. If an error occurs during commit processing, then the remote transaction must respond to the gateway with SEND_ERR to indicate that the commit failed.
One special case for the use of PGA_CONFIRM=ACCEPT is with IMS/TM version 7. When using the "implied APPC" support that is provided by IMS/TM version 7, conversations that run at SYNCLEVEL 1 are handled differently than conversations that run at SYNCLEVEL 0. IMS/TM automatically generates CONFIRM requests after each APPC SEND when the conversation is at SYNCLEVEL 1. On the gateway side, if PGA_CONFIRM=ACCEPT is not specified, then the CONFIRM requests sent by IMS/TM result in errors generated by the gateway. Using PGA_CONFIRM=ACCEPT alleviates this problem, allowing the gateway to respond to incoming CONFIRM requests with CONFIRMED responses. The only limitation with running this way is that the implied APPC support provided by IMS does not notify the application when a CONFIRM request is received from the gateway. This means that the gateway cannot use CONFIRM to implement COMMIT, thereby disabling the use of COMMIT and ROLLBACK to control updates on the IMS side of the conversation.
A.1.4 Sample listener.ora file for a Gateway Using SNA
PK=j 8j PK >A
OEBPS/ch9.htmJ{
Configuring the SNA Communication Package on Solaris
9 Configuring the SNA Communication Package on Solaris
Oracle Database Gateway for APPC uses the SNA Advanced Program to Program Communication (APPC/LU6.2) protocol to communicate with an OLTP. APPC support on Solaris Operating System (SPARC 64-bit) is provided by the SNAP-IX product.
This chapter describes how to configure SNAP-IX on a Solaris system to run Oracle Database Gateway for APPC.
Many OLTPs provide options for manipulating the security conduct of an inbound (client) APPC session request. Refer to the appropriate documentation for your OLTP for detailed information about this issue.
Note that for CICS, the gateway provides the following support:
ATTACHSEC=LOCAL, ATTACHSEC=IDENTIFY, ATTACHSEC=VERIFY, and ATTACHSEC=MIXIDPE are fully supported by the gateway.
ATTACHSEC=PERSISTENT, specified in the CICS CONNECTION definition, requires capability that is not yet available in the gateway.
9.2 Configuring SNAP-IX Version 6
The following sections describe how to configure SNAP-IX version 6.
9.2.1 Before You Begin
This section requires you to specify parameters that are unique to your system to configure SNAP-IX version 6 properly. Before you begin, request these parameters from your network administrator.
9.2.2 SNAP-IX Configuration Tool
All of the SNAP-IX product configuration is done using the xsnaadmin program. This tool is an X-Windows application that provides a graphical interface to view and modify the current SNAP-IX configuration and the current running state of the host SNA node.
9.2.3 Creating SNAP-IX Profiles for the Gateway
Oracle Database Gateway for APPC requires a stored set of definitions, called Side Information Profiles, to support connections between the gateway and gateway servers. Each profile consists of a profile name and a profile type, which is a set of fields describing the profile. The fields in a given profile type are generally a mix of operating parameter values and names of other SNA profiles relevant to the profile. Each functional part of APPC, such as the Mode, Remote Transaction Program name, and Logical Unit (LU), is described by a distinct profile type.
9.2.4 Independent Versus Dependent LUs
The gateway configuration can accommodate either independent or dependent LUs. If you choose to use dependent LUs, or are restricted to using dependent LUs, the gateway functions properly. If a dependent LU is correctly defined, then you do not need to make changes to the configuration of the gateway, nor should any changes be needed to the gateway server. However, Oracle recommends that you use independent LUs for the gateway because they support multiple parallel sessions or conversations. This means that multiple Oracle client applications can be active simultaneously with the same gateway server through the independent LU.
In contrast to independent LUs, dependent LUs support only a single active session. The CP (Control Point for the Node) queues each additional conversation request from the gateway behind an already active conversation. In other words, conversations are single-threaded for dependent LUs.
The operational impact of dependent LUs is that the first client application can initiate a conversation through the gateway with the gateway server, but while that session is active (which could be for seconds, minutes, or hours, depending on how the client application and transaction are designed), any other client application initiating a session with the same gateway server appears to hang as it waits behind the previous session.
If a production application really uses only a single conversation at any one time, then there should not be a problem. However, at some point, you might require additional concurrent conversations for testing or for other application development. Having more than one conversation requires that additional dependent LUs be defined on the remote host. Additional configuration entries must be added to SNAP-IX. Additional Side Information Profiles should be defined to use the new dependent LUs. Gateway instances should be created and configured to use these new Side Information Profiles.
9.2.5 Creating SNA Definitions for the Gateway
SNAP-IX definitions are stored in the following files, which are located in the /etc/opt/sna directory:
SNA node definitions: sna_node.cfg
SNA domain definitions: sna_domn.cfg
These files are created and maintained with the xsnaadmin tool. Maintenance of SNA definitions is usually done by a user with administrative authority. The following information is intended for a user creating SNA definitions for the gateway. You must have some knowledge of SNA before reading this section.
9.2.6 Sample SNAP-IX Definitions
The $ORACLE_HOME/dg4appc/sna subdirectory contains a set of sample SNAP-IX definition files for the gateway, which are created with the xsnaadmin. These sample files are sna_domn.cfg and sna_node.cfg. SNA definitions are very specific to the host and SNA network. As such, the sample definitions provided will not work without being tailored for the local host and SNA network.
9.2.7 Configuring SNAP-IX
This section describes the process of creating SNA definitions for SNAP-IX, using xsnaadmin. All configuration is done using the various dropdown menus and panels in xsnaadmin. The following configuration descriptions follow the samples provided. Please tailor the various SNA values for your local host and SNA network.
9.2.8 Starting xsnaadmin
Use the following commands to invoke xsnaadmin. The DISPLAY environment variable must be set correctly. If you are running xsnaadmin from the local console, then DISPLAY should already be set. If you are running xsnaadmin from a remote X display, then set DISPLAY to the host name or IP address of that display.
On startup of xsnaadmin, the main screen opens and displays the current configuration of the local SNA node.
9.2.8.1 Configuring the SNA node
To configure the SNA node, you need to do the following:
From the Services menu, select Configure Node Parameters.
In the Node Parameters dialog box, enter the APPN support type, Control Point Name, Control Point Alias, and Node ID as needed. The Control Point Name is composed of the SNA Network Name and the CP name of the local host.
Click OK.
9.2.8.2 Adding a Port
To add a new port, from the Services menu, select Connectivity and New Port.
In the Add to Nodename dialog box, select the Port type and click OK.
In the SAP dialog box, enter a Port name and network card number. The Port name is used to logically name the physical network card that you are using and is used to bind a Service Access Port to the card for SNA protocols. Usually, you can accept the values provided in the dialog box. If a different network card is needed, however, enter the card number as reported by the dmesg command.
Click OK.
9.2.8.3 Create a Link Station
When the Port has been defined, you must create a Link Station. The Link Station represents the SNA node of the remote host of the gateway server. But before you create the Link Station, you must create a Remote Node definition as described in the following procedure:
From the Services menu, select APPC and Add Remote Node.
In the dialog box, enter the SNA CPNAME of the remote node and click OK.
Now you can create a Link Station as follows:
From the Services menu, select Connectivity and New Link Station. In the dialog box, select the Port previously defined and click OK.
In the Link Station dialog box, enter a name for the Link Station, choose the SNA Port name, the type of link activation, and the LU Traffic type. For maximum flexibility, select the Any option.
For Independent LU traffic, specify the Remote Node name. Click Remote Node and select the node you previously created, and then click OK. Choose the type of the Remote node, typically a Network node.
For Dependent LU traffic, specify the role of the Remote node, typically 'host', the Local Node ID, and optionally, Remote Node ID.
Specify the Contact Information. Contact information contains the MAC address of the remote host as well as the SAP number.
Click Advanced for additional parameters of the Link Station. The Token Ring Parameters dialog box shows additional parameters of the Link Station. These parameters affect initial XID contact and retransmission times and limits. You usually do not need to change the default values.
Click OK.
9.2.8.4 Creating Local LUs
When the Remote Node definitions have been made, create the Local LU names for the local host as follows:
From the Services menu, select APPC and New Local LU. In the local LU dialog box, enter the name of the local LU and an alias. This name must correspond to the VTAM definitions on the remote gateway server host for the UNIX host.
Click OK.
9.2.8.5 Creating Partner LUs
Now define a Partner LU that represents the LU that the gateway server is using to communicate.
From the Services menu, select APPC and New Partner LUs and Partner LU on Remote Node.
In the Partner LU dialog box, enter the Partner LU name and characteristics. The Partner LU name contains the SNA Network Name as well as the LU name of the remote LU. Enable parallel session support. The location is the name as the Remote Node name. You can click Location for a list.
Click OK.
9.2.8.6 Creating Mode and CPI-C Profiles
When the local and remote LU definitions have been created, create the necessary Mode and CPI-C definitions.
From the Services menu, select APPC and Modes. In the Modes dialog box, click New to add a new mode.
In the Mode dialog box, enter the Mode Name and other session parameters. The recommended name for a gateway mode is CICSPGA. Contact your Remote Host system administrator for appropriate mode parameters.
Click OK.
Now that the Mode has been defined, create the CPI-C Side Information Profile, which the gateway uses as a connection name. From the menu, select APPC and CPI-C.
In the CPI-C destination names dialog box, click New to add a new Profile.
In the CPI-C destination dialog box, enter the Profile name, Local LU name, Partner TP, Partner LU and mode, and Security option. The partner TP name is the name of the host transaction program or a dummy value to be overridden in the TIP.
For the Local LU, you may specify a specific LU or choose the default LU. For the Partner LU, enter either the full LU name or the alias created previously.
Enter ORAPLU62 for the mode name. Choose the type of security for these sessions to use. This affects how session authorization is done.
Click OK.
9.2.9 Testing the Connection
Before proceeding with gateway configuration tasks, ensure that your connection is working. Perform this by starting the SNAP-IX Node and then starting the individual link stations.
Figure 9-1 shows the relationship between SNAP-IX definitions and the VTAM definitions on the remote host.
Figure 9-1 Relationship Between SNAP-IX Definitions and Host VTAM Definitions
When you have finished configuring the SNA communication package for Solaris, proceed to Chapter 10, "Configuring the OLTP" to continue configuring the network.
PKQAJ J PK >A OEBPS/img_text/g6_1vtam.htm
Description of the illustration g6_1vtam.eps
This figure shows the relationship between SNA profiles and the Host VTAM definitions. The surrounding text describes the concepts.
PK3 PK >A OEBPS/img_text/g8_1vtam.htmy
Description of the illustration g8_1vtam.eps
Figure 9-1 illustrates the relationship between SNAP-IX definitions and the remote host VTAM definitions. The concepts are adequately described in the surrounding text.
End of description.
PKl?~ y PK >A OEBPS/img_text/g6_1sna.htm
Description of the illustration g6_1sna.eps
This figure shows the relationship between SNA Server definitions and the VTAM definitions.
PKgW PK >A OEBPS/img_text/g1_1trms.htmM
Description of the illustration g1_1trms.eps
This figure shows the relationship between the gateway and the Oracle database on a UNIX host. The client is connected to the Oracle database, which is connected to the gateway, which holds the gateway remote procedure calls and PGAU, via Oracle Net. They are connected to the OLTP in the Mainframe via TCP/IP or SNA. Figure 1-1 is adequately described in the text surrounding it.
End of description.
PKR M PK >A OEBPS/img_text/g7_1vtam.htmn
Description of the illustration g7_1vtam.eps
Figure 8-1 illustrates the relationship between SNAPlus2 definitions and the remote host definitions. The surrounding text adequately describes the concepts.
End of description.
PK&s n PK >A OEBPS/img_text/g1_2arch.htmm
Description of the illustration g1_2arch.eps
Figure 1-2 provides an illustration of the gateway architecture . The components of the gateway are described adequately in the text surrounding the figure.
End of description.
PKTgr m PK >A OEBPS/ch12.htm
Gateway Configuration Using SNA Communication Protocol
11 Gateway Configuration Using SNA Communication Protocol
This chapter describes how to configure the Oracle database for a gateway using the SNA protocol on your UNIX platform. It also shows you how to configure commit-confirm, should you choose to implement it.
This chapter provides the steps necessary to verify installation and configuration of the gateway components, including optional commit-confirm. It contains the following sections:
Configuring the Oracle Database Gateway for APPC using SNA involves working with the following components:
Oracle database
UNIX system
Network
OLTP
11.1 Before You Begin
This chapter requires you to input parameters unique to your system to properly configure the gateway and SNA communications interface.
Refer to Appendix D, "Configuration Worksheet" for a worksheet listing the installation parameters that you need to know before you can complete the configuration process. Ask your network administrator to provide you with these unique parameter names before you begin.
11.2 Preparing to Configure a Gateway Installation/Upgrade
There are three ways to establish the gateway-Oracle database relationship when you are installing or upgrading or migrating the gateway:
Depending on the location of the gateway and the Oracle database, you might need to transfer some of the gateway administrative files to the location where Oracle database is installed.
Follow the instructions corresponding to your combination of the gateway-Oracle database locations listed below.
When Oracle Database and the Gateway Are Installed in the Same ORACLE_HOME
When Oracle Database and the Gateway Are Installed on Separate Systems
You need to perform the following tasks if Oracle database and the gateway are installed on separate systems:
Locate the gateway administrative files in the gateway $ORACLE_HOME/dg4appc/admin directory. All files in this directory that have the .sql, .pkh, or .pkb suffixes must be copied into a similarly-named directory in the Oracle database Oracle home directory.
Now locate the gateway demo files and subdirectories in the $ORACLE_HOME/dg4appc/demo directory of the gateway. Copy the pgavsn.sql and pgaecho.sql files into a similarly named directory in Oracle database.
Copy the other subdirectories and files related to your installed OLTP on your remote host. For example, if you have CICS as your only OLTP, then copy the $ORACLE_HOME/dg4appc/demo/CICS gateway files into a similarly named directory in the Oracle database.
Note:
Before transferring the files from the $ORACLE_HOME/dg4appc/demo directory, ensure that you have generated your required TIPs. You need to transfer the TIPs as well.
Now create the directories with the following commands:
$ cd $ORACLE_HOME
$ mkdir dg4appc
$ mkdir dg4appc/admin
Use whatever file transfer mechanism is available on your system to copy all of the .sql, .pkh, and .pkb files from the gateway Oracle home $ORACLE_HOME/dg4appc/admin directory to the Oracle database Oracle home $ORACLE_HOME/dg4appc/admin directory.
You might also transfer the demo files from the gateway directory to the Oracle database directory. Copy the files and directory recursively from the gateway Oracle home $ORACLE_HOME/dg4appc/demo directory to the Oracle database $ORACLE_HOME/dg4appc/demo directory.
Before transferring the files from the $ORACLE_HOME/dg4appc/demo directory, ensure that you have generated your required TIPs. You need to transfer the TIPs as well.
Follow these steps to configure your Oracle database if you have installed Oracle Database Gateway for APPC for the first time:
Ensure that the UTL_RAW PL/SQL package has been installed on your Oracle database. All PGAU-generated TIP specifications use UTL_RAW, which provides routines for manipulating raw data.
Use SQL*Plus to connect to the Oracle database as the SYS user.
From SQL*Plus, enter the following command:
SQL> DESCRIBE UTL_RAW
The DESCRIBE statement produces output on your screen. If you browse through the output, you should see some functions, including a compare function. If you do not see this output, then continue the UTL_RAW installation by performing step d below.
If the DESCRIBE statement indicates success, then your Oracle database has UTL_RAW installed and you can proceed to Step 2.
Use SQL*Plus to connect to the Oracle database as the SYS user.
From SQL*Plus, run the utlraw.sql and prvtrawb.plb scripts in the Oracle database $ORACLE_HOME/rdbms/admin directory, in the following order:
Ensure that the DBMS_OUTPUT standard PL/SQL package is enabled on Oracle database. The sample programs and installation verification programs on the distribution media use this standard package.
If necessary, use SQL*Plus to connect to the Oracle database as the SYS user.
From SQL*Plus, enter the following command:
SQL> DESCRIBE DBMS_OUTPUT
The DESCRIBE statement produces output on your screen. If you browse through that output, you should see some functions, including a put_line function.
If you do not see this output, then you must create the DBMS_OUTPUT package. Refer to the Oracle Database Rules Manager and Expression Filter Developer's Guide for more information about creating the DBMS_OUTPUT package. After successful installation of the DBMS_OUTPUT package, issue the DESCRIBE statement.
If the DESCRIBE statement indicates success, then your Oracle database has DBMS_OUTPUT created, and you can proceed to Step 3.
Install the UTL_PG PL/SQL package. All PGAU-generated TIP specifications use UTL_PG, which provides routines for performing numeric conversions to and from raw data.
If necessary, use SQL*Plus to connect to the Oracle database as the SYS user.
From SQL*Plus, run the utlpg.sql and prvtpgb.plb scripts in the Oracle database $ORACLE_HOME/rdbms/admin directory, in the following order:
If necessary, use SQL*Plus to connect to the Oracle database as the SYS user.
Enter the following command:
SQL> DESCRIBE HS_FDS_CLASS
The DESCRIBE statement produces output on your screen. If the DESCRIBE statement indicates success, then heterogeneous services catalogs have been created on your Oracle database and you can proceed to Step 5, otherwise follow the next step only if the DESCRIBE statement does not indicate success. Step c creates the Heterogeneous Services catalog.
If it is necessary to create the Heterogeneous Services catalog, enter the following command:
SQL> $ORACLE_HOME/rdbms/admin/caths.sql
Create a public database link to access Oracle Database Gateway for APPC:
Use SQL*Plus to connect to the Oracle database as the SYSTEM user. You can use the following SQL*Plus sample whether the Oracle database and the gateway are on the same system or on different systems. In the following sample, pgasrv is the tns_name_entry that will be assigned to the gateway when you modify the tnsnames.ora file later in this chapter.
SQL> CREATE PUBLIC DATABASE LINK PGA USING 'PGASRV'
Create the gateway administrator user PGAADMIN and install the PG DD.
Use SQL*Plus to connect to the Oracle database as the SYSTEM user.
From SQL*Plus, run the pgacr8au.sqlscript in the $ORACLE_HOME/dg4appc/admin directory. This script creates the PGAADMIN user ID.
The initial password defined for PGAADMIN is PGAADMIN. Use the ALTER USER command to change the password. For more information about password issues, refer to the Oracle Database SQL Language Reference.
SQL> @$ORACLE_HOME/dg4appc/admin/pgacr8au.sql
Use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the pgddcr8.sqlscript in the $ORACLE_HOME/dg4appc/admin directory. This script installs the PG DD.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddcr8.sql
From SQL*Plus, connect to the Oracle database as the SYS user.
Grant execution privileges on DBMS_PIPE to PGAADMIN:
SQL> GRANT EXECUTE ON DBMS_PIPE TO PGAADMIN
Install the TIP trace access PL/SQL routines. These routines require that the DBMS_PIPES standard PL/SQL package is installed and that PGAADMIN has execute privileges on it. For more information on DBMS_PIPES, refer to the Oracle Database Rules Manager and Expression Filter Developer's Guide.
If necessary, use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the pgatiptr.sql script in the $ORACLE_HOME/dg4appc/admin directory. This script creates PL/SQL routines that can be called to read and purge trace information created by PGAU-generated TIP specifications. It also creates public synonyms for these routines. The script prompts you for the necessary user IDs and passwords.
SQL> @$ORACLE_HOME/dg4appc/admin/pgatiptr.sql
Install the GPGLOCAL package. This package is required for compilation and execution of all PGAU-generated TIP specifications. TIP developers should be granted execute privileges on GPGLOCAL (refer to Step 3 of "Optional Configuration Steps to Permit Multiple Users").
Use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the gpglocal.pkh script in the $ORACLE_HOME/dg4appc/admin directory. This script compiles the GPGLOCAL package specification.
SQL> @$ORACLE_HOME/dg4appc/admin/gpglocal.pkh
From SQL*Plus, run the gpglocal.pkb script in the $ORACLE_HOME/dg4appc/admin directory. This script compiles the GPGLOCAL package body.
SQL> @$ORACLE_HOME/dg4appc/admin/gpglocal.pkb
11.4 Upgrading or Migrating the Oracle Database from Previous Gateways
Follow these instructions only if you have a previous version of the Oracle Database Gateway for APPC installed on your system and need to configure it for Release 11.2 of the gateway.
Upgrade your Oracle Database Gateway for APPC to current version levels as follows:
Use SQL*Plus to connect to the Oracle database as the SYS user.
Install the UTL_RAW package body. From SQL*Plus, run the prvtrawb.plbscript from the $ORACLE_HOME/rdbms/admin directory. This script upgrades the UTL_RAW package body.
SQL> @$ORACLE_HOME/rdbms/admin/prvtrawb.plb
Install the UTL_PG package body. From SQL*Plus, run the prvtpgb.plbscript from the $ORACLE_HOME/rdbms/admin directory. This script upgrades the UTL_PG package body.
SQL> @$ORACLE_HOME/rdbms/admin/prvtpgb.plb
The prvtrawb.plb and prvtpgb.plb scripts should complete successfully. If they fail because specifications do not exist or were invalidated, then consider reinstalling the package specifications as directed in the following section.
11.4.1 If You Must Reinstall Package Specifications
If the UTL_RAW or UTL_PG package has been invalidated or deinstalled, the prvtrawb.plb and prvtpgb.plb scripts might not complete successfully and you might have to reinstall the package specifications.
If you do reinstall the package specifications, any dependent objects (such as existing user TIPs and client applications) are invalidated and will subsequently need to be recompiled. The impact of this is a one-time performance delay while recompilation of the TIPs and dependent client applications proceeds.
Important:
Before proceeding with reinstallation of the package scripts, make sure that you are in the $ORACLE_HOME/dg4appc/admin directory.
TIPs were split into separate specification and body files in release 3.3 to avoid cascaded recompilations in later releases.
Step 1 Run the Following Scripts before Proceeding with the PGAU Upgrade
From SQL*Plus, run the utlraw.sql script:
If necessary, use SQL*Plus to connect to the Oracle database as the SYS user.
From SQL*Plus, run the utlraw.sql and utlpg.sql scripts in Oracle database $ORACLE_HOME/rdbms/admin directory, in the following order, to upgrade their respective package specifications:
TIPs and dependent client applications must be recompiled after reinstallation of the package specifications. Refer to the "Compiling a TIP" section in Chapter 3 of the Oracle Database Gateway for APPC User's Guide for information about compiling TIPs.
11.4.2 Upgrading PGAU From Previous Gateway Releases
Upgrade the PG DD as follows before executing the new PGAU:
If necessary, use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the pgddupgr.sqlscript in the $ORACLE_HOME/dg4appc/admin directory. This script upgrades the PG DD.
11.5 Configuring the Oracle Database for Gateways to Coexist
You might have an older version of the gateway already installed. Be aware that although a version 10 gateway can communicate with a version 9 data dictionary (PGDD), a version 9 gateway cannot communicate with a version 10 data dictionary. Thus, if you upgrade your data dictionary to a version 10, no gateways which were configured with a version 9 data dictionary will be able to communicate with it.
11.6 Optional Configuration Steps to Permit Multiple Users
The following configuration steps are optional. Perform these steps if you want to allow users other than PGAADMIN to perform PG DD operations using PGAU.
Create public synonyms for the PG DD to allow other users to access the tables:
Use SQL*Plus to connect to the Oracle database as the SYSTEM user.
From SQL*Plus, run the pgddcr8s.sql script in the $ORACLE_HOME/dg4appc/admin directory. This script creates public synonyms for the PG DD.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddcr8s.sql
Create roles for accessing the PG DD, performing definitions of transactions, and generating TIP specifications. The PGAADMIN user can grant these roles to other users as necessary.
Use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the pgddcr8r.sql script in the $ORACLE_HOME/dg4appc/admin directory. This script creates two roles, PGDDDEF and PGDDGEN. The PGDDDEF role provides SELECT, INSERT, UPDATE, and DELETE privileges against some of the PG DD tables, and SELECT privileges against others, and allows execution of the PGAU DEFINE, GENERATE, REDEFINE, REPORT, and UNDEFINE statements. The PGDDGEN role provides select privileges against the PG DD tables, and allows execution of the PGAU GENERATE and REPORT statements only.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddcr8r.sql
Grant access to PGA required packages.
TIP developers require access to the following PL/SQL packages, which are shipped with the Oracle database:
DBMS_PIPE in the $ORACLE_HOME/rdbms/admin directory
UTL_RAW in the $ORACLE_HOME/rdbms/admin directory
UTL_PG in the $ORACLE_HOME/rdbms/admin directory
Explicit grants to execute these packages must be made to TIP developers.
These grants can be private as in the following example:
$ sqlplus SYS/pw@database_specification_string
SQL> GRANT EXECUTE ON UTL_RAW TO tip_developer;
SQL> GRANT EXECUTE ON UTL_PG TO tip_developer;
SQL> GRANT EXECUTE ON DBMS_PIPE TO tip_developer;
SQL> CONNECT PGAADMIN/pw@database_specification_string
SQL> GRANT EXECUTE ON PGAADMIN.PURGE_TRACE TO tip_developer;
SQL> GRANT EXECUTE ON PGAADMIN.READ_TRACE TO tip_developer;
SQL> GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO tip_developer;
SQL> exit
Alternatively, these grants can be public as in the following example:
$ sqlplus SYS/pw@database_specification_string
SQL> GRANT EXECUTE ON UTL_RAW TO PUBLIC;
SQL> GRANT EXECUTE ON UTL_PG TO PUBLIC;
SQL> GRANT EXECUTE ON DBMS_PIPE to PUBLIC;
SQL> CONNECT PGAADMIN/pw@database_specification_string
SQL> GRANT EXECUTE ON PGAADMIN.PURGE_TRACE TO PUBLIC;
SQL> GRANT EXECUTE ON PGAADMIN.READ_TRACE TO PUBLIC;
SQL> GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO PUBLIC;
SQL> EXIT
You can use either private or public grants. Both are sufficient for using PGA. Public grants are easier and can be performed now. If you use private grants, then they must be issued each time a new TIP developer user ID is created.
SQL scripts for performing these grants are provided in the $ORACLE_HOME/dg4appc/admin directory. Thepgddapub.sql script performs these grants for public access to the packages. The pgddadev.sql script performs the grants for private access to the packages by a single TIP developer. If you are going to use private grants, then you must run the pgddadev.sql script once for each TIP developer user ID:
Use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the appropriate script (pgddapub.sql or pgddadev.sql) from the $ORACLE_HOME/dg4appc/admin directory. The script performs the necessary grants as described earlier. You are prompted for the required user IDs, passwords, and database specification strings.
If you are using private grants, then repeat this step for each user ID requiring access to the packages.
If you are upgrading from a previous release of the gateway, and if you want to upgrade your existing TIPs with new function and maintenance, then regenerate existing TIP specifications using the PGAU GENERATE statement.
Note:
The PGAU has been enhanced to automatically upgrade existing PG DD entries with a new attribute when a PGAU GENERATE command is executed. To support this enhancement, add a new privilege to the PGDDGEN role. To do this, as the PGAADMIN user, use SQL*Plus to connect to the Oracle database where the PG DD is stored. Then issue the following SQL command:
SQL> GRANT INSERT ON PGA_DATA_VALUES TO PGDDGEN
Invoke PGAU in the directory path where the PGAU control files are generated and where TIPs are stored:
To configure the gateway, perform the following steps:
Tailor the Oracle Database Gateway for APPC parameters.
Parameters specific to the gateway are supplied in the gateway parameter file, initsid.ora, which is in the $ORACLE_HOME/dg4appc/admin directory. A sample gateway parameter file, initPGA.ora is provided in this subdirectory.
Note:
In the initsid.ora file, substitute your dg4appc SID name for "sid " in this file name.
The initsid.ora file contains both APPC and TCP/IP parameters, separated by a description. You must modify the initsid.ora file by deleting the TCP/IP parameters. Refer to Appendix A, "Gateway Initialization Parameters for SNA Protocol" for the valid APPC parameters.
The parameters fall into two categories:
Gateway initialization parameters
These parameters control the general operation of the gateway in the Oracle environment.
Important:
Before performing the following step, refer to Appendix A, "Gateway Initialization Parameters for SNA Protocol" for information about tailoring gateway initialization and PGA parameters. Pay special attention to the information about using the PGA_CAPABILITY parameter.
PGA parameters
PGA parameters control the APPC interface portion of the gateway. Use the SET gateway initialization parameter to specify PGA parameters. Oracle recommends that you group all SET commands for PGA parameters at the end of the initsid.ora file.
Note:
Misspelled parameters are ignored. However, if the $ORACLE_HOME/dg4appc/admin/initsid.ora file is missing, all calls to the gateway fail and return a PGA-20928 error.
11.8 Configuring Commit-Confirm
Note:
If you are planning to implement commit-confirm, read the detailed explanation of commit-confirm's capabilities in Chapter 5 of the Oracle Database Gateway for APPC User's Guide, "Implementing Commit-Confirm (SNA Only) before proceeding.
Follow these steps to configure the commit-confirm components. The steps for configuring commit-confirm include:
Configuring the Oracle database where the gateway server will store its transaction log information
Configuring the gateway initialization parameters
Configuring the OLTP
All of these steps must be performed before attempting to use any applications that use commit-confirm.
11.8.1 Configuring the Oracle Database for Commit-Confirm
The Oracle database installation where the gateway server will store its transaction log information should ideally be on the same system where the gateway runs. The configuration of the server consists of creating the gateway DBA user, creating the commit-confirm log tables and creating the PL/SQL stored procedure used by the gateway server for logging transactions.
The pgaccau.sql script from the $ORACLE_HOME/dg4appc/admin directory creates the gateway DBA user ID. The default user ID is PGADBA with the initial password set to PGADBA. If you want to change the user ID or initial password, you must modify the script.
Use SQL*Plus to connect to the Oracle database as the SYSTEM user.
From SQL*Plus, run the pgaccau.sql script from the $ORACLE_HOME/dg4appc/admin directory. This script creates the gateway DBA user ID. If you want to change the password at any time after running this script, you can use the ALTER USER command to change the password. For further information, refer to the Oracle Database SQL Language Reference.
Use SQL*Plus to connect to Oracle database as the PGADBA user.
From SQL*Plus, run the pgaccpnd.sql script from the $ORACLE_HOME/dg4appc/admin directory. This script creates the PGA_CC_PENDING table used by the gateway server for its commit-confirm transaction log.
From SQL*Plus, run the pgacclog.sql script from the $ORACLE_HOME/dg4appc/admin directory. This script creates the PGA_CC_LOGPL/SQL stored procedure used by the gateway server for updating the PGA_CC_PENDING table.
Disconnect from Oracle database.
11.8.2 Configuring Gateway Initialization Parameters for Commit-Confirm
These parameters should be added to your initsid.ora file, where sid is the gateway SID for your commit-confirm gateway.
11.8.3 Configuring the OLTP for Commit-Confirm
Configuration of the OLTP includes defining and installing the following:
Commit-confirm transaction log database
Commit-confirm forget or recovery transaction
Sample commit-confirm applications provided with the gateway
Note:
A restart of the OLTP may be necessary to implement the changes required for commit-confirm support. You should plan for this with your OLTP system administrator.
Detailed instructions for configuring the Transaction Server for z/OS and IMS/TM are provided in the $ORACLE_HOME/dg4appc/demo/CICS/README.doc and $ORACLE_HOME/dg4appc/demo/IMS/README.doc files, respectively.
11.9 Verifying the Gateway Installation and OLTP Configuration
To verify the gateway installation and the OLTP configuration, perform the following procedures after installing Oracle Database Gateway for APPC. In addition, if you chose to configure commit-confirm, follow the steps to verify the OLTP configuration for commit-confirm.
To verify the gateway software installation using the database link PGA previously created, perform the following steps:
Using SQL*Plus, connect to your Oracle database as PGAADMIN.
Run $ORACLE_HOME/dg4appc/demo/pgavsn.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/pgavsn.sql
The server version number banner appears at your terminal. The following output appears:
Oracle Database Gateway for APPC.
Version 11.2.0.0.2 Thu Jun 11 14:39:15
2009
Copyright (c) Oracle Corporation 1979,2009. All rights reserved.
PL/SQL procedure successfully completed.
Run $ORACLE_HOME/dg4appc/demo/pgaecho.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/pgaecho.sql
You will receive the following output:
==> Congratulations, your installation was successful. <==
11.9.2 Verifying the OLTP Configuration
The procedure for verifying your OLTP configuration varies, depending on which OLTP you are using and depending upon which platform the OLTP is running on. CICS Transaction Server for z/OS, IMS/TM, APPC/MVS, and z/OS are the currently supported OLTPs. Follow the instructions in the following sections for verifying installation:
If your OLTP is CICS Transaction Server for z/OS, perform the following steps to verify the CICS configuration.
To verify that the FLIP transaction is installed correctly, log on to your CICS Transaction Server for z/OS and enter the following transaction, replacing FLIP with the transaction ID you chose for FLIP when you configure your CICS Transaction Server for z/OS for the gateway:
FLIPTHIS MESSAGE
The following output appears:
EGASSEM SIHT PILF
Log on to HP-UX.
Modify the pgacics.sql file, which is located at $ORACLE_HOME/dg4appc/demo/CICS/pgacics.sql. Customize the following three items used for accessing the gateway and the CICS Transaction Server for z/OS as described in the comments at the beginning of the file:
CICS transaction ID
Side Profile name
Logmode entry name
Ensure that the SNA communication package on your system has been started.
Log on to your CICS Transaction Server for z/OS and run this transaction, where name is the name of the CONNECTION definition installed by the DFHCSDUP job run in the CICS configuration steps:
CEMT SET CONNECTION(name) ACQUIRED
This transaction activates the CICS connection to HP-UX.
Use SQL*Plus to connect to your Oracle database as PGAADMIN.
Run pgacics.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/CICS/pgacics.sql
The following message appears:
==> Congratulations, your gateway is communicating with CICS <==
Your CICS Transaction Server for z/OS installation verification is complete.
11.9.2.2 IMS/TM Verification
If your OLTP is IMS/TM, then perform the following steps to verify the IMS/TM configuration:
To verify that the FLIP transaction is installed correctly, log on to your IMS/TM system and enter the following transaction, replacing FLIP with the transaction ID you chose for FLIP when you configured your IMS/TM system for the gateway:
FLIP THIS MESSAGE
The following output appears on your terminal:
EGASSEM SIHT PILF
Log on to HP-UX.
Modify the pgaims.sql file, which is located at $ORACLE_HOME/dg4appc/demo/IMS/pgaims.sql. Customize the following three items used for accessing the gateway and the IMS/TM system as described in the comments at the beginning of the file:
IMS/TM transaction ID
Side Profile Name
Logmode entry name
Ensure that the SNA communication package on your system has been started.
Use SQL*Plus to connect to Oracle database as PGAADMIN.
Run pgaims.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/IMS/pgaims.sql
The following message appears:
==> Congratulations, your gateway is communicating with IMS/TM <==
Your IMS/TM installation verification is now complete.
11.9.2.3APPC/MVS Verification
If your OLTP is APPC/MVS, perform the following steps to verify the APPC/MVS configuration:
Verify that your APPC/MVS subsystem is active.
Log on to HP-UX
Modify the pgamvs.sql file, which is located at $ORACLE_HOME/dg4appc/demo/MVS/pgamvs.sql. Customize the following three items used for accessing the gateway and the APPC/MVS system as described in the comments at the beginning of the file:
APPC/MVS transaction ID
Side Profile Name
Logmode entry name
Ensure that the SNA communication package on your system has been started.
Use SQL*Plus to connect to your Oracle database as PGAADMIN.
Run pgamvs.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/MVS/pgamvs.sql
The following message appears:
=> Congratulations, your gateway is communicating with APPC/MVS <=
Your APPC/MVS installation verification is now complete.
11.9.3 Verifying OLTP Configuration for Commit-Confirm
Refer to Chapter 5, "Implementing Commit-Confirm" in the Oracle Database Gateway for APPC User's Guide for background information on the components and capabilities of commit-confirm.
Samples are provided with the gateway for Transaction Server for z/OS and IMS/TM for implementing commit-confirm support. They are in the following directories, respectively: $ORACLE_HOME/dg4appc/demo/CICS and $ORACLE_HOME/dg4appc/demo/IMS. A README.doc file in each directory provides detailed information about installing and using the samples. JCL files for compiling and linking the sample programs are provided as well. The samples included with the gateway assist you with the following:
Creating and initializing the commit-confirm transaction log databases and defining those databases to the OLTP
For Transaction Server for z/OS, the sample uses a VSAM file for the log database. For IMS/TM, a SHISAM/VSAM database is used.
Using subroutines for receiving the Oracle Global Transaction ID from the gateway and logging it into the commit-confirm transaction log database
These subroutines are provided in the pgacclg.asm files. They can be used in your applications to reduce the complexity of the code changes to your programs. For Transaction Server for z/OS, the subroutine provided is called using the EXEC CICS LINK interface. For IMS/TM, the subroutine provided is called using the standard CALL statement or its equivalent in the application programming language. Both of these subroutines are written in 370 assembler to eliminate any interlanguage interface complexities and compiler dependencies.
Forget and recovery transactions
These are provided in the pgareco.asm files. Forget and recovery transactions must be installed into your OLTP and accessible through APPC so that the gateway can invoke them to forget a transaction once it has been successfully committed, and to query transaction state during recovery processing. These transactions delete the entry for a particular Oracle Global Transaction ID from the OLTP commit-confirm transaction log database during forget processing, and query the entry for a particular Oracle Global Transaction ID from the OLTP commit-confirm transaction log database during recovery processing. For both Transaction Server for z/OS and IMS/TM, these transactions are written in 370 assembler.
Using the sample commit-confirm transaction log databases and subroutines
For Transaction Server for z/OS, a sample DB2 update transaction, DB2C, is provided in the pgadb2c.cob file. This is a COBOL example that updates the DB2 sample EMP table. For IMS/TM, a sample DLI update transaction, PGAIMSU, is provided in the pgaimsu.cob file. This is a COBOL example that updates the DLI sample PARTS database.
11.10 Performing Postinstallation Procedures
The following are optional steps that you can perform as necessary. Installation of the sample applications for your OLTP is recommended to help you to fully understand how the gateway works and how it interfaces with your OLTP.
11.10.1 Installing Sample Applications
Oracle Database Gateway for APPC package contains the following sample PL/SQL procedures and OLTP transaction programs that demonstrate the capabilities of the gateway.
APPC/MVS
z/OS data set information
CICS Transaction Server for z/OS
DB2 inquiry
DB2 multi-row inquiry
DB2 update
VSAM inquiry
VSAM update
DLI inquiry
FEPI DB2 inquiry
FEPI VSAM inquiry
IMS/TM
IMS inquiry using IVTNO and IVTNV sample transactions
IMS PARTS inquiry (CPI-C)
IMS PARTS update (CPI-C)
Additional samples are added to the distribution media in later releases of the product. Wherever possible, sample applications use the sample databases provided with the database products.
For this release, full documentation on installing and using the sample applications is available in the following directories and files:
PKa PK >A
OEBPS/toc.ncx
Oracle® Database Gateway for APPC Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64, 11g Release 2 (11.2)CoverTable of ContentsList of FiguresList of TablesOracle Database Gateway for APPC Installation and Configuration Guide, 11g Release 2 (11.2) for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64PrefaceIntroduction to Oracle Database Gateway for APPCRelease InformationSystem RequirementsInstalling the GatewayConfiguring Your Oracle NetworkConfiguring the SNA Communication Package on LinuxConfiguring the SNA Communication Package on AIX-Based SystemsConfiguring the SNA Communication Package on HP-UXConfiguring the SNA Communication Package on SolarisConfiguring the OLTPGateway Configuration Using SNA Communication ProtocolGateway Configuration Using TCP/IP Communication ProtocolSecurity RequirementsMigration From Existing GatewaysGateway Initialization Parameters for SNA ProtocolGateway Initialization Parameters for TCP/IP Communication ProtocolGateway TerminologyConfiguration WorksheetIndexCopyright
PKGq PK >A
OEBPS/ch5.htm$
Configuring Your Oracle Network
5 Configuring Your Oracle Network
This chapter describes how to configure the network.
5.1Configuring the Oracle Network for the Gateway
The instructions in this section will show you how to configure the network if the gateway is utilizing the SNA or TCP/IP communication protocol.
The gateway must be defined to the Oracle Net Listener, and a service name must be defined for accessing the gateway. To do this, perform the following steps:
Add an entry for the gateway to the listener.orafile:
where: /oracle/pga/11.2 is the gateway Oracle home and PGA is the gateway SID name.
Add a service name for the gateway to the tnsnames.ora file on the system where your Oracle database is located. The service name is specified in the USING parameter of the database link defined for accessing the gateway from the Oracle database. For example, if you are using the IPC protocol adapter and your gateway sid is PGA, then add the following entry to tnsnames.ora:
In this example, key is the IPC key defined in the listener.ora file for the IPC protocol. You can use the IPC protocol only if the Oracle database and the gateway are on the same system.
If you are using the TCP/IP protocol adapter, and if your gateway sid is PGA, then add the following entry to tnsnames.ora:
In this example, port is the TCP port defined in the listener.ora file for the TCP protocol, and gateway is the TCP/IP host name of the system where the gateway is located.
Note:
For the following cases:
If your gateway and Oracle database are not on the same system,
If the gateway and the Oracle database are on the same system but the Oracle database Listener is different than the gateway listener
You must define the Oracle database to PGAU by adding a service name to tnsnames.ora on the system where your gateway is located. For example:
Proceed with Configuring the Communication Package for the Gateway
If your communication protocol is SNA, you must now configure the SNA communication package profiles for APPC connections.
Configure the profiles to define LU6.2 conversations with the OLTP. Refer to the appropriate chapter from the following list to read about the SNA communication package or the TCP/IP package for your platform.
PK $ $ PK >A OEBPS/content.opf#1
Oracle® Database Gateway for APPC Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64, 11g Release 2 (11.2)en-USE12078-01Oracle CorporationOracle CorporationOracle® Database Gateway for APPC Installation and Configuration Guide for AIX 5L Based Systems (64-Bit), HP-UX Itanium, Solaris Operating System (SPARC 64-Bit), Linux x86, and Linux x86-64, 11g Release 2 (11.2)2009-07-30T16:20:33ZProvides Oracle Database Gateway installation and configuration information.
PKs}## # PK >A
OEBPS/lof.htm
List of Figures
PKѩe e PK >A OEBPS/ch13.htm
Gateway Configuration Using TCP/IP Communication Protocol
12 Gateway Configuration Using TCP/IP Communication Protocol
This chapter describes how to configure Oracle database for a gateway using TCP/IP for IMS Connect on your UNIX platform. It also provides the steps necessary to verify installation and configuration of the gateway and OLTP components. This chapter contains the following sections:
Configuring Oracle Database Gateway for APPC using TCP/IP support for IMS Connect involves working with the following components:
Oracle database
UNIX system
Network
OLTP
12.1 Before You Begin
This chapter requires you to input parameters unique to your system to correctly configure the gateway and TCP/IP communications interface.
Refer to Appendix D, "Configuration Worksheet" for a worksheet listing the installation parameters that you will need to know before you can complete the configuration process. Ask your network administrator to provide you with these unique parameter names before you begin.
12.2 Preparing to Configure a Gateway Installation/Upgrade
There are three ways to establish the gateway and Oracle database relationship when you are installing, upgrading, or migrating the gateway:
Depending on the location of your gateway and your Oracle database, you might need to transfer some of the gateway administrative files to the location where Oracle database is installed.
Follow the instructions applicable to your combination of the gateway-Oracle database locations listed below.
When Oracle Database and the Gateway Are Installed in the Same ORACLE_HOME
When Oracle Database and the Gateway Are Installed on Separate Systems
When Oracle database and the gateway are installed on separate systems, you need to perform the following tasks:
Locate the gateway administrative files in the gateway $ORACLE_HOME/dg4appc/admin directory. All files in this directory that have the suffix .sql, .pkh, and .pkb must be copied into a similarly named directory in the Oracle database Oracle home directory.
Now, locate the gateway demo files and subdirectories in the gateway $ORACLE_HOME/dg4appc/demo directory. Copy the pgavsn.sql and pgaecho.sql files into a similarly named directory on Oracle database.
Copy the pgaims.sql file from the gateway Oracle home $ORACLE_HOME/dg4appc/demo/IMS directory to the Oracle database Oracle home $ORACLE_HOME/dg4appc/demo/IMS directory.
Optional Steps: If you want to run IVTNV and IVTNO, then you will need to copy the ivtno.ctl, ivtnod.sql, ivtnv.ctl, and ivtnvd.sql files into the Oracle database Oracle home at $ORACLE_HOME/dg4appc/demo/IMS directory as well. Ensure that you generate the required TIPs and transfer them as well.
When Oracle Database and the Gateway Are on the Same System but in Different Directories
You must change your gateway Oracle home to the Oracle database Oracle home directory.
For example, if your gateway Oracle home is set as follows:
$ echo $ORACLE_HOME
/oracle/pga/11.2
and the server Oracle home is located in the /oracle/pga/11.2 directory, then you need to do the following:
Use whatever file transfer mechanism is available on your system to copy all of the .sql, .pkh, and .pkb files from the gateway Oracle home $ORACLE_HOME/dg4appc/admin directory to the Oracle database Oracle home $ORACLE_HOME/dg4appc/admin directory.
You might also transfer the demo files from the gateway directory to the Oracle database directory. Copy the pgavsn.sql and pgaecho.sql files and directory recursively from the gateway Oracle home $ORACLE_HOME/dg4appc/demo directory to the Oracle database $ORACLE_HOME/dg4appc/demo directory.
You might also copy the pgaims.sql file from the gateway Oracle home $ORACLE_HOME/dg4appc/demo/IMS directory to the Oracle database Oracle home $ORACLE_HOME/dg4appc/demo/IMS directory.
Optional Steps: If you want to run IVTNV and IVTNO, then you will need to copy the ivtno.ctl, ivtnod.sql, ivtnv.ctl, and ivtnvd.sql files into the Oracle database Oracle home $ORACLE_HOME/dg4appc/demo/IMS directory as well. Ensure that you generate the required TIPs and transfer them as well.
Follow these steps to configure your Oracle database after installing the Oracle Database Gateway for APPC.
Ensure that the UTL_RAW PL/SQL package has been installed on Oracle database. All TIP specifications generated by Procedural Gateway Administrative Utility (PGAU) use UTL_RAW, which provides routines for manipulating raw data.
Use SQL*Plus to connect to Oracle database as the SYS user.
From SQL*Plus, enter the following command:
SQL> DESCRIBE UTL_RAW
The DESCRIBE statement produces output on your screen. If you browse through the output, then you should see some functions, including a compare function. If you do not see this output, then continue the UTL_RAW installation by performing Step d below.
If the DESCRIBE statement indicates success, then Oracle database has UTL_RAW installed and you can proceed to Step 2.
Use SQL*Plus to connect to Oracle database as SYS.
From SQL*Plus, run the utlraw.sql and prvtrawb.plb scripts in the Oracle database $ORACLE_HOME/rdbms/admin directory in the following order:
Ensure that the DBMS_OUTPUT standard PL/SQL package is enabled on Oracle database. The sample programs and installation verification programs on the distribution media use this standard package.
If necessary, use SQL*Plus to connect to the Oracle database as the SYS user.
Enter the following command:
SQL> DESCRIBE DBMS_OUTPUT
The DESCRIBE statement produces output on screen. If you browse through that output, then you should see some functions, including a put_line function.
If you do not see this output, then you must create the DBMS_OUTPUT package. Refer to the Oracle Database Rules Manager and Expression Filter Developer's Guide for more information about creating the DBMS_OUTPUT package. After installing the DBMS_OUTPUT package successfully, run the DESCRIBE statement.
If the DESCRIBE statement indicates success, then Oracle database has DBMS_OUTPUT created and you can proceed to Step 3.
Install the UTL_PG PL/SQL package. All PGAU-generated TIP specifications use UTL_PG, which provides routines for performing numeric conversions to and from raw data.
If necessary, use SQL*Plus to connect to Oracle database as the SYS user.
From SQL*Plus, run the utlpg.sql and prvtpgb.plb scripts in the Oracle database $ORACLE_HOME/rdbms/admin directory in the following order:
If necessary, use SQL*Plus to connect to Oracle database as the SYS user.
Enter the following command:
SQL> DESCRIBE HS_FDS_CLASS
The DESCRIBE statement produces output on your screen. If the DESCRIBE statement indicates success, then heterogeneous services catalogs have been created on Oracle database and you can proceed to Step 5.
If the DESCRIBE statement does not indicate success, then you must create Heterogeneous Services catalogs, and you must follow Step c below:
If it is necessary to create the Heterogeneous Services catalog, then enter the following command:
SQL> @$ORACLE_HOME/rdbms/admin/caths.sql
Create a public database link to access the Oracle Database Gateway for APPC:
Use SQL*Plus to connect to the Oracle database as the SYSTEM user. You can use the following SQL*Plus sample whether the Oracle database and the gateway are on the same system or on different systems. In the following sample, pgasrv is the tns_name_entry that will be assigned to the gateway when you modify the tnsnames.ora file later in this chapter.
SQL> CREATE PUBLIC DATABASE LINK PGA USING 'PGASRV'
Create the gateway administrator user (PGAADMIN) and install the PG DD.
Use SQL*Plus to connect to Oracle database as the SYSTEM user.
From SQL*Plus, run the pgacr8au.sqlscript in the $ORACLE_HOME/dg4appc/admin directory. This script creates the PGAADMIN user ID.
The initial password defined for PGAADMIN is PGAADMIN. Use the ALTER USER command to change the password. For further information about password issues, refer to the Oracle Database SQL Language Reference.
SQL> @$ORACLE_HOME/dg4appc/admin/pgacr8au.sql
Use SQL*Plus to connect to the Oracle database as PGAADMIN.
From SQL*Plus, run the pgddcr8.sqlscript in the $ORACLE_HOME/dg4appc/admin directory. This script installs the PG DD.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddcr8.sql
From SQL*Plus, connect to the Oracle database as the SYS user.
Grant execute privileges on DBMS_PIPE to PGAADMIN:
SQL> GRANT EXECUTE ON DBMS_PIPE TO PGAADMIN
Ensure that the pg4tcpmap package has been installed on your Oracle database. Follow Steps a through c to test for proper installation of pg4tcpmap.
Use SQL*Plus to connect to Oracle database as the SYSTEM user.
Enter the following command:
SQL> select owner, table_name
from dba_tables
where table_name = 'PGA_TCP_IMSC',
and owner = 'PGAADMIN';
SQL> column owner format a 10
SQL> column index_name format a 18
SQL> column table_name format a 14
SQL> select owner, index_name, table_name
from dba_indexes
where index_name = 'PGA_TCP_IMSC_IND';
Each SELECT statement must produce one row. The following output is the result of the first SELECT statement:
If the SELECT statements produce the preceding output on your screen, then you can skip to Step 8. If the SELECT statement produces no output or more than one row, then the result is not the same as the output described above, and it is necessary for you to perform Step 1.
From SQL*Plus, run the pgaimsc.sql script in the Oracle database $ORACLE_HOME/dg4appc/admin directory:
SQL> @$ORACLE_HOME/dg4appc/admin/pgaimsc.sql
Install the TIP trace access PL/SQL routines. These routines require that the DBMS_PIPES standard PL/SQL package is installed and that PGAADMIN has execute privileges on it. For more information on DBMS_PIPES, refer to the Oracle Database Rules Manager and Expression Filter Developer's Guide.
If necessary, use SQL*Plus to connect to the Oracle database as user PGAADMIN.
From SQL*Plus, run the pgatiptr.sql script in the $ORACLE_HOME/dg4appc/admin directory. This script creates PL/SQL routines that can be called to read and purge trace information created by PGAU-generated TIP specifications. It also creates public synonyms for these routines. The script prompts you for the necessary user IDs and passwords.
SQL> @$ORACLE_HOME/dg4appc/admin/pgatiptr.sql
Install the GPGLOCAL package. This package is required for compilation and execution of all PGAU-generated TIP specifications. TIP developers should be granted execute privileges on GPGLOCAL (refer to Optional Configuration Steps to Permit Multiple Users).
Use SQL*Plus to connect to Oracle database as PGAADMIN.
From SQL*Plus, run the gpglocal.pkh script in the $ORACLE_HOME/dg4appc/admin directory. This script compiles the GPGLOCAL package specification.
SQL> @$ORACLE_HOME/dg4appc/admin/gpglocal.pkh
From SQL*Plus, run the gpglocal.pkb script in the $ORACLE_HOME/dg4appc/admin directory. This script compiles the GPGLOCAL package body.
SQL> @$ORACLE_HOME/dg4appc/admin/gpglocal.pkb
Note:
Recompile TIPs when changing communication protocol from SNA to TCP/IP:
If you have existing TIPs that were generated previously on a gateway using the SNA communication package protocol and you want to utilize the new TCP/IP feature, then the TIPs have to be regenerated by PGAU with certain mandatory NLS_LANGUAGE and Side Profile Settings. Specify the correct ASCII character set in the DEFINE TRANSACTION command.
This is because the gateway assumes that the correct user exit in IMS Connect is being used, which would translate between the correct ASCII and EBCDIC character sets.
12.4 Upgrading or Migrating the Oracle Database from Previous Gateways
Follow these instructions only if you have a previous version of the Oracle Database Gateway for APPC installed on your system and need to configure it for Release 11.2 of the gateway.
Upgrade your Oracle Database Gateway for APPC to current version levels as follows:
Use SQL*Plus to connect to Oracle database as the SYS user.
Install the UTL_RAW package body. From SQL*Plus, run the prvtrawb.plbscript from the $ORACLE_HOME/rdbms/admin directory. This script upgrades the UTL_RAW package body.
SQL> @$ORACLE_HOME/rdbms/admin/prvtrawb.plb
Install the UTL_PG package body. From SQL*Plus, run the prvtpgb.plbscript from the $ORACLE_HOME/rdbms/admin directory. This script upgrades the UTL_PG package body.
SQL> @$ORACLE_HOME/rdbms/admin/prvtpgb.plb
The prvtrawb.plb and prvtpgb.plb scripts should complete successfully. If they fail because specifications do not exist or were invalidated, then consider reinstalling the package specifications as directed in the following section.
12.4.1 If You Must Reinstall Package Specifications
If the UTL_RAW or UTL_PG package has been invalidated or deinstalled, then the prvtrawb.plb and prvtpgb.plb scripts might not complete successfully. You may have to reinstall the package specifications.
If you do reinstall the package specifications, then any dependent objects (such as existing user TIPs and client applications) are invalidated and subsequently need to be recompiled. The impact of this is a one-time performance delay while recompilation of the TIPs and dependent client applications proceeds.
Important:
Before proceeding with reinstallation of the package scripts, ensure that you are in the $ORACLE_HOME/dg4appc/admin directory.
TIPs were split into separate specification and body files in release 3.3 to avoid cascaded recompilations in later releases.
Step 1 Run the Following Scripts Before Proceeding with the PGAU Upgrade
From SQL*Plus, run the utlraw.sql script:
If necessary, use SQL*Plus to connect to the Oracle database as the SYS user.
From SQL*Plus, run the utlraw.sql and utlpg.sql scripts in the Oracle database $ORACLE_HOME/rdbms/admin directory, in the following order, to upgrade their respective package specifications:
TIPs and dependent client applications must be recompiled after reinstallation of the package specifications. Refer to the "Compiling a TIP" section in Chapter 3 of the Oracle Database Gateway for APPC User's Guide for information about compiling TIPs.
12.4.2 Upgrading PGAU from Previous Gateway Releases
Upgrade the PG DD as follows before running the new PGAU:
If necessary, use SQL*Plus to connect to Oracle database as the PGAADMIN user.
From SQL*Plus, run the pgddupgr.sqlscript in the $ORACLE_HOME/dg4appc/admin directory. This script upgrades the PG DD.
12.5 Optional Configuration Steps to Permit Multiple Users
The following configuration steps are optional. Perform these steps if you want to allow users other than PGAADMIN to perform PG DD operations using PGAU.
Create public synonyms for the PG DD to allow other users to access the tables:
Use SQL*Plus to connect to Oracle database as the SYSTEM user.
From SQL*Plus, run the pgddcr8s.sql script in the $ORACLE_HOME/dg4appc/admin directory. This script creates public synonyms for the PG DD.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddcr8.sql
Create roles for accessing the PG DD, performing definitions of transactions, and generating TIP specifications. The PGAADMIN user can grant these roles to other users as necessary.
Use SQL*Plus to connect to Oracle database as user PGAADMIN.
From SQL*Plus, run the pgddcr8r.sql script in the $ORACLE_HOME/dg4appc/admin directory. This script creates two roles, PGDDDEF and PGDDGEN. The PGDDDEF role provides SELECT, INSERT, UPDATE, and DELETE privileges against some of the PG DD tables, and SELECT privileges against others, and allows execution of the PGAU DEFINE, GENERATE, REDEFINE, REPORT, and UNDEFINE statements. The PGDDGEN role provides select privileges against the PG DD tables and allows execution of the PGAU GENERATE and REPORT statements only.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddcr8r.sql
Grant access to PGA required packages.
TIP developers require access to the following PL/SQL packages, which are shipped with Oracle database:
DBMS_PIPE in the $ORACLE_HOME/rdbms/admin directory
UTL_RAW in the $ORACLE_HOME/rdbms/admin directory
UTL_PG in the $ORACLE_HOME/rdbms/admin directory
Explicit grants to run these packages must be made to TIP developers.
These grants can be private as in the following example:
$ sqlplus SYS/ pw@database_specification_string
SQL> GRANT EXECUTE ON UTL_RAW TO tip_developer;
SQL> GRANT EXECUTE ON UTL_PG TO tip_developer;
SQL> GRANT EXECUTE ON DBMS_PIPE TO tip_developer;
SQL> CONNECT PGAADMIN/ pw@database_specification_string
SQL> GRANT EXECUTE ON PGAADMIN.PURGE_TRACE TO tip_developer;
SQL> GRANT EXECUTE ON PGAADMIN.READ_TRACE TO tip_developer;
SQL> GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO tip_developer;
SQL> EXIT
Alternatively, these grants can be public as in the following example:
$ sqlplus SYS/pw@ database_specification_string
SQL> GRANT EXECUTE ON UTL_RAW TO PUBLIC;
SQL> GRANT EXECUTE ON UTL_PG TO PUBLIC;
SQL> GRANT EXECUTE ON DBMS_PIPE to PUBLIC;
SQL> CONNECT PGAADMIN/ pw@database_specification_string
SQL> GRANT EXECUTE ON PGAADMIN.PURGE_TRACE TO PUBLIC;
SQL&gUt; GRANT EXECUTE ON PGAADMIN.READ_TRACE TO PUBLIC;
SQL> GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO PUBLIC;
SQL> EXIT
You can use either private or public grants. Both are sufficient for using PGA. Public grants are easier and can be performed now. If you use private grants, then they must be given each time a new TIP developer user ID is created.
SQL scripts for performing these grants are provided in the $ORACLE_HOME/dg4appc/admin directory. Thepgddapub.sql script performs these grants for public access to the packages. The pgddadev.sql script performs the grants for private access to the packages by a single TIP developer. If you are going to use private grants, then you must run the pgddadev.sql script once for each TIP developer user ID:
Use SQL*Plus to connect to Oracle database as PGAADMIN.
From SQL*Plus, run the appropriate script (pgddapub.sql or pgddadev.sql) from the $ORACLE_HOME/dg4appc/admin directory. The script performs the necessary grants as described earlier. You are prompted for the required user IDs, passwords, and database specification strings. If you are using private grants, then repeat this step for each user ID requiring access to the packages.
If you are using private grants, then repeat this step for each user ID requiring access to the packages.
SQL> @$ORACLE_HOME/dg4appc/admin/pgddapub.sql
or
SQL> @$ORACLE_HOME/dg4appc/admin/pgddadev.sql
If you are upgrading from a previous release of the gateway when the communication protocol was SNA, to the current gateway using TCP/IP, and if you want to upgrade your existing TIPs with new function and maintenance, then regenerate existing TIP specifications using the PGAU GENERATE statement.
Note:
The PGAU has been enhanced to automatically upgrade existing PG DD entries with a new attribute when a PGAU GENERATE command is executed. To support this enhancement, add a new privilege to the PGDDGEN role. To do this as the PGAADMIN user, use SQL*Plus to connect to the Oracle database installation where the PG DD is stored. Then issue the following SQL command:
SQL> GRANT INSERT ON PGA_DATA_VALUES TO PGDDGEN
Start PGAU from the directory path where the PGAU control files are generated and where TIPs are stored:
You must now configure the TCP/IP for IMS Connect communication package profiles for TCP/IP connections.
Configure the profiles to define the TCP/IP conversations with the OLTP.
When you have finished configuring your communications package, return to the following section "Configuring the Gateway",.
12.7 Configuring the Gateway
To configure the gateway, perform the following:
Tailor the gateway parameters.
There are a number of parameters specific to Oracle Database Gateway for APPC when it is using TCP/IP for IMS Connect. These are supplied in the gateway parameter file, initsid.ora, which is in the $ORACLE_HOME/dg4appc/admin directory. A sample gateway parameter file, initPGA.ora is provided in this subdirectory.
Note:
In the initsid.ora file, substitute your gateway SID name for "sid " in this file name.
The initsid.ora file contains both APPC and TCP/IP parameters separated by a description. You must modify the initsid.ora file by deleting the APPC parameters. Refer to "Gateway Initialization Parameter File Using TCP/IP" for the valid TCP/IP parameters.
The parameters fall into two categories:
Gateway initialization parameters
These parameters control the general operation of the gateway in the Oracle environment.
Important:
Before performing the following step, refer to "Gateway Initialization Parameter File Using TCP/IP" for information about tailoring gateway initialization and PGA parameters. Pay special attention to the information about using the PGA_CAPABILITY parameter.
PGA parameters
PGA parameters control the TCP/IP interface portion of the gateway. Use the SET gateway initialization parameter to specify PGA parameters. Oracle recommends that you group all SET commands for PGA parameters at the end of the initsid.ora file.
Note:
Misspelled parameters are ignored. However, if the $ORACLE_HOME/dg4appc/admin/initsid.ora file is missing all calls to the gateway fail and return a PGA-20928 error.
12.8 Loading the PGA_TCP_IMSC Table
Gateway users who want to employ the TCP/IP protocol do so by using the pg4tcpmap tool.
The pg4tcpmap tool is located on the gateway. Its function is to map the Side Profile Name to TCP/IP and IMS Connect attributes. You must run this tool before executing the PL/SQL gateway statements (such as $ORACLE_HOME/dg4appc/demo/IMS/pgaims.sql).
In PGAINIT TIP, for example, the user must specify a Side Profile Name. The SNA protocol recognizes and utilizes the parameter. In this release of the gateway, the pg4tcpmap tool uses the original PGAINIT TIP format to map the relevant SNA parameters to TCP/IP. The pg4tcpmap tool inserts the values of these parameters into a table called PGA_TCP_IMSC.
12.9 Verifying the Gateway Installation and OLTP Configuration
To verify the gateway installation and the OLTP configuration, perform the following procedures after installing the gateway.
Note:
If your database link name is not "PGA," modify the demonstration .sql files to give them the particular database link name that you created in Step 5 of Configuring Oracle Database: First-Time Installation. You must modify the following .sql files:
pgavsn.sql
pgaecho.sql
pgaims.sql
12.9.1 Verifying the Gateway Installation
To verify the gateway software installation using the database link PGA previously created, perform the following steps:
Using SQL*Plus, connect to your Oracle database as PGAADMIN.
Run $ORACLE_HOME/dg4appc/demo/pgavsn.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/pgavsn.sql
The server version number banner appears at your terminal. The following output appears:
Oracle Database Gateway for APPC (extension TCP/IP for IMS connect).
Version
11.2.0.0.2 Thu Jun 11 14:52:36 2009
Copyright (c) Oracle Corporation 1979,
2009. All rights reserved.
PL/SQL procedure successfully completed.
Run $ORACLE_HOME/dg4appc/demo/pgaecho.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/pgaecho.sql
You will receive the following output:
==> Congratulations, your installation was successful. <==
12.9.2 Verifying the OLTP Configuration
Use the following procedure to verify your OLTP configuration.
Perform the following steps to verify the IMS/TM configuration. Be certain that you have installed and configured the IMS Connect and that it is up and running before you begin this procedure. Refer to the IBM IMS Connect Guide and Reference for information about how to perform the installation and configuration tasks.
Note:
TIPs must be recompiled when changing communication protocol to TCP/IP.
TCP/IP only: If you have existing TIPs that were generated previously on a gateway using the SNA communication package protocol and you want to utilize the new TCP/IP feature, then the TIPs will have to be regenerated by PGAU with mandatory NLS_LANGUAGE and Side Profile Settings. Specify the appropriate ASCII character set in the DEFINE TRANSACTION command.
This is because the gateway assumes that the appropriate user exit in IMS Connect is being used, which would translate between the appropriate ASCII and EBCDIC character sets.
To verify that the FLIP transaction is installed correctly, log on to your IMS/TM system and enter the following transaction (replacing FLIP with the transaction ID you chose for FLIP when you configured your IMS/TM system for the gateway):
Modify the pgaims.sqlfile, which is located at $ORACLE_HOME/dg4appc/demo/IMS/pgaims.sql. Customize the following three items used for accessing the gateway and the IMS/TM system as described in the comments at the beginning of the file:
IMS/TM transaction ID
Side Profile Name
Logmode entry name
Ensure that the TCP/IP communication protocol on your system has been started.
Using SQL*Plus, connect to your Oracle database from PGAADMIN.
Run pgaims.sql.
SQL> @$ORACLE_HOME/dg4appc/demo/IMS/pgaims.sql
The following message appears:
==> Congratulations, your gateway is communicating with IMS/TM <==
Your IMS/TM installation verification is now complete.
12.10 Performing Postinstallation Procedures
The following are optional steps that you can perform as necessary. Installation of the sample applications for your OLTP is recommended to help you to fully understand how the gateway works and how it interfaces with your OLTP.
12.10.1 Installing Sample Applications
Your Oracle Database Gateway for APPC featuring TCP/IP for IMS Connect contains sample PL/SQL procedures and OLTP transaction programs that demonstrate the gateway's capabilities.
Note:
When you call a gateway that uses TCP/IP as the communication protocol, and you use EBCDIC as the language in the control files, then you must change the language from EBCDIC to ASCII. Some examples of control files that might be in EBCDIC language are ivtno.ctl and ivtnv.ctl.
For more information, refer to the $ORACLE_HOME/dg4appc/demo/IMS/ivtno.ctl and $ORACLE_HOME/dg4appc/demo/IMS/ivtnv.ctl files.
Samples are provided for IMS/TM:
IMS inquiry using IVTNO and IVTNV sample transactions
Additional samples are added to the distribution media in newer releases of the product. Wherever possible, the sample applications use the sample databases provided with the database products.
For this release, the entire documentation about installing and using the sample applications is available in:
This section includes the following terms and definitions used in this edition of the Oracle Database Gateway for APPC Installation and Configuration Guide:
dg4pwd is a utility which encrypts passwords that are normally stored in the gateway initialization file. Passwords are stored in an encrypted form in the password file, making the information more secure. Refer to "Passwords in the Gateway Initialization File" for detailed information about how the dg4pwd utility works.
tg4tcpmap tool
This gateway mapping tool is applicable only when the gateway is using TCP/IP support for IMS Connect. Its function is to map the Side Profile Name to TCP/IP and IMS Connect attributes into the PGA_TCP_IMSC table.
PGA (Procedural Gateway Administration)
PGA is a general reference within this guide to all or most components constituting the Oracle Database Gateway for APPC. This term is used when references to a specific product or component are too narrow.
PGDL (Procedural Gateway Definition Language)
PGDL is the collection of statements used to define transactions and data to the PGAU.
This is a precompiled PL/SQL procedure that is stored in Oracle database.
UTL_RAW PL/SQL Package (the UTL_RAW Functions)
This component of the gateway represents a series of data conversion functions for PL/SQL RAW variables and remote host data. The types of conversions performed depend on the language of the remote host data. Refer to Appendix D of the Oracle Database Gateway for APPC User's Guide for more information.
UTL_PG PL/SQL Package (the UTL_PG Functions)
This component of the gateway represents a series of COBOL numeric data conversion functions. Refer to NUMBER_TO_RAW and RAW_TO_NUMBER argument values in Appendix C of the Oracle Database Gateway for APPC User's Guide for supported numeric data type conversions.
PKBD PK >A
OEBPS/ch7.htmHT
Configuring the SNA Communication Package on AIX-Based Systems
7 Configuring the SNA Communication Package on AIX-Based Systems
The Oracle Database Gateway for APPC uses the SNA Advanced Program to Program Communication (APPC/LU6.2) protocol to communicate with online transaction processing (OLTP). All AIX-based system support for APPC is provided by IBM SNA server product.
This product requires a stored set of definitions, called profiles, to support connections between the gateway and the applications using OLTP. Each profile consists of a profile name, a profile type, and a set of fields describing the profile. The fields in a profile type are generally a mixture of operating parameter values and names of other SNA profiles relevant to the profile.
Refer to this chapter if your gateway uses the SNA communication protocol. This chapter describes how to create and activate SNA server profiles.
Note:
When you finish following the instructions in this chapter to configure your communication protocol, refer to Chapter 5, "Configuring Your Oracle Network" to continue your network configuration.
Many OLTPs provide options for manipulating the security conduct of an inbound (client) APPC session request. Refer to the appropriate OLTP documentation for detailed information about this topic.
Note:
For CICS, one security option is not supported by the gateway. ATTACHSEC=PERSISTENT, specified on the CICS CONNECTION definition, requires capability that is not yet available in the gateway.
However, ATTACHSEC=LOCAL, ATTACHSEC=IDENTIFY, ATTACHSEC=VERIFY, and ATTACHSEC=MIXIDPE are fully supported by the gateway.
7.2 Independent Versus Dependent LUs
Oracle recommends independent LUs for Oracle Database Gateway for APPC because they support multiple parallel sessions or conversations. This means that multiple Oracle client applications can be active simultaneously with the same OLTP through the independent LU.
Dependent LUs support only a single active session. The CP (SNA server for AIX, in this case) queues additional conversation requests from the gateway server behind an already active conversation. In other words, conversations are single threaded for dependent LUs.
If a dependent LU is correctly defined, then you do not need to alter the Oracle Database Gateway for APPC configuration, the host transaction, or how the OLTP is started.
The operational impact of dependent LUs is that the first client application can initiate a conversation through the Oracle Database Gateway with the OLTP. While that transaction is active (which could be seconds to minutes to hours depending on how the client application and transaction are designed), any other client application initiating a conversation with the same OLTP instance appears to hang as it waits behind the previous conversation.
If a production application really uses only a single conversation or transaction at a time, then there should be no impact.
However, additional concurrent conversations or transactions might be required for testing or for other application development. Each requires that additional dependent LUs be defined on the remote host, plus additional SNA server profiles, which define the additional dependent LUs on the IBM pSeries workstation. The TIP that initiates the conversation must specify the different Partner LU through a different side information profile or by overriding the LU name.
You can create and modify the SNA server profile definitions using menus in the AIX System Management Interface Tool (smit).
Maintenance of SNA server profiles is normally done by a user with root access. The following information is intended for the user who creates profiles for the gateway. You should have some knowledge of SNA before reading this section.
By using smit, you should be able to accept most of the defaults. The default values assigned to many of the fields in a new set of profiles are acceptable for the gateway.
The $ORACLE_HOME/dg4appc/sna subdirectory contains a sample set of profiles for the gateway in the pgasna.export file.
Before building the SNA server profiles, examine the appropriate sample export file to determine the profiles needed, their contents, and their interrelationships. The export file format is text-oriented, and each field of each profile is clearly labeled. You can print a copy of the export file to use while working with the profiles in a smit session.
7.4 Profile Types
Several types of SNA server profiles are relevant to gateway APPC/LU6.2 operation. Each profile can be created and edited using a corresponding smit menu that can be reached from the Communications Applications and Services primary menu choice.
The profiles are presented in hierarchical order. The profile types that are lowest in the hierarchy are discussed first. This matches the logical sequence in which to create the profiles. You can use the smit list menu to specify the profile names.
7.5 SNA Server Profiles
Refer to the appropriate vendor documentation for a complete discussion of SNA profiles. This section is an overview of SNA server profiles in relation to the Oracle Database Gateway for APPC. It includes the following topics:
The SNA node profile defines miscellaneous SNA system defaults. Set the "Maximum number of sessions" and "Maximum number of conversations" fields to values large enough to handle the maximum number of concurrent gateway conversations anticipated, plus any non-gateway sessions and conversations that are in use on your system by other applications.
Set the "Recovery Resource Manager (RRM) enabled?" field to no, unless you already have other applications running on your AIX system that require this field to be set to yes. For example, CICS pSeries and Encina need this field set to yes.
7.5.2 Link Station Profile
The Link Station Profile and the related DLC profile describe and control the connection of the IBM pSeries to the network. Details on profile contents are not discussed here because Oracle Database Gateway for APPC does not impose special requirements on these profiles. The sample profile distributed inpgasna.export includes a profile created for a Token-Ring network connection. The Link Station Profile name is specified later in the Partner LU Location Profile, if one is necessary.
7.5.3 Mode Profile
The Mode Profile specifies parameters that determine:
APPC/LU6.2 parallel session limits
send and receive pacing values
SNA RU size
the mode name that is sent to OLTP at session initiation
The mode name that you specify must be defined to the OLTP communications software. Choose the mode name in addition to the other mode parameters after consulting the user who is responsible for configuring the OLTP communications software.
The parameters that are related to parallel session limits determine the maximum number of concurrent conversations allowed between a gateway instance and the OLTP. This equates to the maximum number of concurrently active remote transaction program invocations through the gateway instance.
The mode name, for example, ORAPLU62, is specified later in the Side Information Profile.
Note:
Do not confuse the Mode Profile with the mode name.
7.5.4 Local LU Profile
The Local LU (Logical Unit) Profile describes the SNA LU through which the gateway communicates.
An LU name must be assigned to the gateway. The LU name assigned to the gateway might be required elsewhere in the SNA network. Contact the SNA network administrator to determine the correct LU name to specify in the profile.
Set the "Local LU name" to the LU name assigned to the gateway.
An alias should be assigned to the LU using the "Local LU alias" field. This alias is used later in the side information profile.
Set the "Local LU is dependent" field to no.
The Local LU Profile name is specified later in the side information profile.
7.5.5 Partner LU Profile
The Partner LU Profile describes the SNA LU of the OLTP system with which the gateway communicates. The name of the OLTP LU and the name of your SNA network must be specified in this profile. Contact your SNA network administrator to determine the correct LU and network names.
Set the "Fully qualified partner LU name" field to the network name, followed by a period, followed by the OLTP LU name. For example, network.oltplu.
You can assign an alias to the partner LU name by setting the "Partner LU alias" to the value of your choice. This enables you to reference the partner LU without knowing the fully qualified partner LU name and minimizes the change if the partner LU name is changed.
Set the "Parallel sessions supported?" field to yes unless your OLTP does not support parallel sessions.
If you plan to use SNA session or conversation security, then set the "Session security supported?" and "Conversation security supported?" fields as required. These settings require the Session Security and Conversation Security Profiles.
See Also:
The vendor documentation for more information
7.5.6 Partner LU Location Profile
The Partner LU Location Profile is used when the remote host where the Partner LU is located is not an APPN-capable node. Many mainframe systems do not have APPN capability. For example, z/OS systems running VTAM versions before version 4 do not support APPN. Also, if your hardware connection is through a front-end processor running NCP versions before version 5, then APPN is not supported. In these cases, the Partner LU Location Profile can be used to specify the name of the System Services Control Point (SSCP) or Control Point (CP), which owns the network connection to the partner LU.
Set the "Fully qualified partner LU name" field to the network name, followed by a period, followed by the OLTP LU name For example, network.oltplu.
Set the "Partner LU location method" and associated fields as required by your network configuration. If you use the owning cp option, then the "Fully qualified owning Control Point (CP) name" field should be set to the SSCP or CP name, which owns the network connection to the partner LU. For VTAM, the SSCP name is the value of the VTAM NETID start parameter, usually found in VTAMLST member ATCSTR00.
7.5.7 Side Information Profile
The side information profile is a required profile, which is used to identify target OLTP systems to be accessed through Oracle Database Gateway for APPC.
The side information profile identifies the following:
the local LU alias
the partner LU alias or fully-qualified name
the remote transaction program name (optional)
the mode name
Set the profile information as follows for each side information profile field:
Set the Local LU or Control Point alias to the alias assigned to the local LU in the Local LU Profile.
Set the Mode name to the actual mode name as specified in the Mode Profile.
Set the Remote transaction program name (RTPN) using the actual remote TP name or a dummy name to be overridden at execution time.
Set the "RTPN in hexadecimal?" field to yes, if the remote TP name is hexadecimal.
If there is a field for "Partner LU alias", then add the alias assigned to the partner LU in the Partner LU Profile.
If there is a field for "Fully qualified partner LU name", then add the fully qualified partner LU name of the partner LU.
Figure 7-1 shows the relationship between SNA server profiles and the VTAM definitions on the host.
Figure 7-1 Relationship Between SNA Profiles and Host VTAM Definitions
After you have built all the necessary SNA server profiles for communicating with the remote host, you must verify the profiles. Use the "Verify Configuration Profiles" option under the "Advanced Configuration" option of the smit SNA server menu. Then use smit to start the link station profile.
See Also:
the vendor documentation for more information about using smit to start link stations
7.7 Resume Configuration of the Gateway
When you finish configuring the SNA communication package for your AIX-based system, proceed to Chapter 10, "Configuring the OLTP" to continue configuring the network.
The gateway architecture involves multiple systems, database servers, and communications facilities, each having distinct security capabilities and limitations. To effectively plan and implement your security scheme, you must understand these capabilities and limitations, in addition to knowing your installation security requirements.
Read this chapter to learn about the capabilities and limitations of the Oracle Database Gateway for APPC. This chapter contains the following sections:
Before implementing your security scheme, you must understand the existing security requirements and expectations in your environment. Because you are enabling application access to different databases on different systems, you may need to merge multiple security cultures. When you connect several different systems into an operating whole, the system with the strictest security requirements generally dictates what the other systems can and cannot do.
Gateway security includes two main concerns:
Users and applications that are permitted access to a particular gateway instance and OLTP
OLTP transactions that users and applications are able to execute
You can control access at several points in the gateway architecture. The primary options are discussed in the following sections. Control over remote transaction program access is provided by each OLTP with native authorization mechanisms based on user ID. These facilities are described in the product documentation for your OLTP. Information in this chapter includes how the gateway facilities determine the user ID that is in effect for a particular OLTP connection.
When the gateway is involved in an RPC request, security mechanisms are in effect for each system component encountered by the gateway. The first system component that is encountered is the application tool or third-generation language (3GL) program. The last system component that is encountered is the OLTP.
Each of the following sections identifies the component and the type of security processing that is available in that component. Each section offers a summary of key features and parameters. Refer to product-specific documentation for detailed information about the non-gateway components for Oracle and non-Oracle products.
13.2 Authenticating Application Logons
An application must connect to an Oracle database before using the gateway. The type of logon authentication that you use determines the resulting Oracle user ID and can affect gateway operation.
The following types of authentication are available:
Oracle authentication
With Oracle authentication, each Oracle user ID has an associated password that is known to Oracle. When an application connects to the server, it supplies a user ID and password. Oracle confirms that the user ID exists and that the password matches the one stored in the database.
Operating system authentication
With operating system authentication, the underlying server operating system is responsible for authentication. An Oracle user ID that is created with the IDENTIFIED EXTERNALLY attribute (instead of a password) is accessed with operating system authentication. To log on with such a user ID, the application supplies a forward slash ( / ) for a user ID and does not supply a password.
To perform operating system authentication, the server determines the requester operating system user ID, optionally adds a fixed prefix to it, and uses the result as the Oracle user ID. The server confirms that the user ID exists and is IDENTIFIED EXTERNALLY, but no password checking is done. The underlying assumption is that users are authenticated when they log on to the operating system.
Operating system authentication is not available on all platforms and is not available in some Oracle Net (client-server) and multithreaded server configurations. Refer to your platform-specific Oracle database documentation and Oracle Database Net Services Administrator's Guide to determine the availability of this feature in your configuration.
The following sections discuss database links for users of the gateway employing either TCP/IP or SNA communications protocols.
13.3.1 Link Accessibility
The first point of control for a database link is simply if it is accessible to a given user. A public database link can be used by any user ID. A private database link can be used only by the user who created it. Database link usability is determined by its ability to open a session to the gateway. Oracle database makes no distinction as to the type of use (such as read-only versus update or write) or which remote objects can be accessed. These distinctions are the responsibility of the OLTP that is accessed.
13.3.2 Links and CONNECT Clauses
The CONNECT clause is another security-related attribute of a database link. You can use the CONNECT clause to specify an explicit user ID and password, which can differ from the Oracle user ID and password. This CONNECT user ID and password combination is sent to the gateway when the database link connection is first opened. Depending on gateway-specific options, the gateway might send that user ID and password to the OLTP to be validated.
If a database link is created without a CONNECT clause using Oracle authentication, then the Oracle user ID and password of the user are sent to the gateway when the connection is opened. If the user logs on to Oracle database with operating system authentication, then the gateway receives no user ID or password from Oracle database. It is impossible for operating system-authenticated Oracle users to use a gateway database link defined without a CONNECT clause. However, if your OLTP provides user ID mapping facilities based on the gateway LU name from which the user is connecting, then such a connection is possible if all users on the same gateway instance can use the same OLTP user ID.
The information in Section 13.4 applies only to the security needs of gateway users employing the SNA communications protocol. When an RPC request to start a remote transaction program is received by the gateway, the gateway attempts to start an APPC conversation with the OLTP. Before the conversation can begin, a session must start between the platform's Logical Unit (LU) and the OLTP LU.
APPC support for your platform is provided by a SNA communication package (SNAP-IX for Solaris Operating System (SPARC), SNAPlus2 for HP-UX and SNA Server for AIX-based systems).
SNA and its various access method implementations, including VTAM and the SNA communication package for your platform, provide security validation at session initiation time, allowing each LU to authenticate its partner. This validation is carried out entirely by network software before the gateway and OLTP application programs begin their conversation and process conversation-level security data. If session-level security is used, then correct password information must be established in your platform's SNA profiles and in similar parameter structures in the OLTP to be accessed. Refer to the appropriate communications software product documentation for detailed information about this subject.
13.4.1 Specifying SNA Conversation Security
The PGA_SECURITY_TYPE parameter of the gateway initialization file allows you to specify one of three options that determine the security conduct of the LU6.2 conversation that is allocated with the OLTP. These options are part of the SNA LU6.2 architecture, but their precise behavior might vary depending on the particular OLTP system.
13.4.1.1 SNA Security Option SECURITY=NONE
If you specify PGA_SECURITY_TYPE=NONE, then the gateway performs no processing of the client user ID and password. The conversation is allocated with SNA option SECURITY=NONE.
13.4.1.2 SNA Security Option SECURITY=PROGRAM
If you specify PGA_SECURITY_TYPE=PROGRAM, then the gateway allocates the conversation with SNA option SECURITY=PROGRAM, and the following information is sent to the OLTP:
If the TIP user ID and password overrides are used, then the specified user ID and password are sent regardless of the database link specification.
If the database link has explicit CONNECT information, then the specified user ID and password are sent.
If the database link has no CONNECT clause, and if the application logged on to Oracle with an explicit user ID and password, then the Oracle user ID and password are sent.
If the application logs on to Oracle with operating system authentication, and if the database link lacks explicit CONNECT information, then no user ID and password are sent. If no user ID and password are sent, and if the OLTP is not configured to assign a default user ID, then the connection fails.
In general, SNA option SECURITY=PROGRAM tells the OLTP to authenticate the user ID/password combination using whatever authentication mechanisms are available. For example, if CICS Transaction Server for z/OS is the OLTP, then RACF can be used. This is not always the case, however, because each OLTP can be configured to process inbound user IDs in other ways.
13.4.1.3 SNA Security Option SECURITY=SAME
If you specify PGA_SECURITY_TYPE=SAME, the gateway allocates the conversation with SNA option SECURITY=SAME and sends only a user ID, without a password, to the OLTP. In this case, your SNA communication package sends the owning user ID of the gateway server executable, $ORACLE_HOME/bin/pg4asrv, as the user ID. The user ID that is sent is not the Oracle user ID. This user ID can be viewed with the UNIX ls command and can be changed by an authorized user with the chown command. Because this user ID is the same for all users of a given gateway instance, this option is of limited use.
Note:
The user ID sent is not translated to uppercase by your SNA communication package. If your OLTP is running on a system which does not allow lowercase user IDs (z/OS, for example), you must set up an uppercase user ID on your platform to be the owner of the gateway executable file.
SECURITY=SAME is similar to your platform operating system authentication. It tells the OLTP that the user has already been authenticated at the originating side of the conversation. There might be configuration parameters or options on the server side that affect whether SECURITY=SAME conversations are accepted. When properly configured, the OLTP only confirms that the user ID itself is valid and then accepts the connection. As with SECURITY=PROGRAM, you can change this using configuration options in many OLTPs.
13.5 TCP/IP Security
The security information in this section applies only to users of the Oracle Database Gateway for APPC using the TCP/IP for IMS Connect feature. When an RPC request to start a remote transaction program is received by the gateway, the gateway attempts to start the TCP/IP conversation with IMS Connect. IMS Connect would contact the OLTP (IMS) through OTMA and XCF. Refer to the IBM IMS Connect Guide and Reference for more information. The conversation between the gateway and IMS Connect occurs when the network uses the TCP/IP address or host name and port number to connect from the gateway to IMS Connect.
Note:
As the gateway is using PGAU to generate TIPs, the TIPs contain SNA information. When using the Oracle Database Gateway for APPC with TCP/IP support for IMS Connect, you need to map the SNA names to the TCP/IP host name and port number in order for the gateway to talk to IMS Connect. Use the pg4tcpmap tool to map the information from SNA to TCP/IP. Refer to Chapter 6, "pg4tcpmap Commands," of the Oracle Database Gateway for APPC User's Guide for more information.
IMS Connect provides validation at session initiation time, allowing each connection to authenticate its partner. This validation is carried out entirely by network software before the gateway and OLTP application programs at IMS begin their conversation and process conversation-level security data. If session-level security is used, then correct password information must be established in your platform and in similar parameter structures in the OLTP to be accessed.
If you specify PGA_SECURITY_TYPE=NONE, then the gateway performs no processing of the client user ID and password.
13.5.1.2 TPC/IP Security Option SECURITY=PROGRAM
If you specify PGA_SECURITY_TYPE=PROGRAM, then the following information is sent to the OLTP:
If the TIP user ID and password overrides are used, then the specified user ID and password are sent regardless of the database link specification.
If the database link has explicit CONNECT information, then the specified user ID and password are sent.
If the database link has no CONNECT clause, and if the application logged on to Oracle with an explicit user ID and password, then the Oracle user ID and password are sent.
If the application logs on to Oracle with operating system authentication, and if the database link lacks explicit CONNECT information, then no user ID and password are sent. If no user ID and password are sent, and if the OLTP is not configured to assign a default user ID, then the connection fails.
RACF is the only authentication mechanism available when the Oracle Database Gateway for APPC using TCP/IP for IMS Connect talks to IMS Connect.
Important:
You must specify your RACF group name through the pg4tcpmap tool if you have set your PGA security option to SECURITY=PROGRAM. For more information about this issue, refer to the Oracle Database Gateway for APPC User's Guide.
13.6 Passwords in the Gateway Initialization File
Initialization parameters may contain sensitive information, such as user IDs or passwords. Initialization parameters are stored in plain text files and may be deemed insecure. An encryption feature has been added to Heterogeneous Services making it possible to encrypt parameters values. This is done through the dg4pwd utility. For more information on this utility refer to Oracle Database Heterogeneous Connectivity User's Guide.
PKstƕ[ [ PK
>Aoa, mimetypePK >Av:Z0 : iTunesMetadata.plistPK >AYu c META-INF/container.xmlPK >ArQ Q
OEBPS/ch8.htmPK >A9 8
X OEBPS/ch3.htmPK >A;rگ: : Ց OEBPS/ch11.htmPK >A[pT O OEBPS/cover.htmPK >AE Q OEBPS/title.htmPK >Adټ, ,
t OEBPS/ape.htmPK >A v v
k OEBPS/ch1.htmPK >A& ]p Xp
V OEBPS/ch4.htmPK >AK}I I
OEBPS/ch6.htmPK >A(}< x<
@B OEBPS/apb.htmPK >Aw,q3 3 ~ OEBPS/preface.htmPK >AI\
ܲ OEBPS/index.htmPK >AsdXV L 7} OEBPS/img/g6_1vtam.gifPK >AՆӡ , OEBPS/img/g7_1vtam.gifPK >AAV A O E ; OEBPS/img/g8_1vtam.gifPK >AZ Z OEBPS/img/g1_2arch.gifPK >AA_.
K OEBPS/ch2.htmPK >AIzH uH OEBPS/ch15.htmPK >A=j 8j
V OEBPS/apa.htmPK >AQAJ J
R OEBPS/ch9.htmPK >A3 OEBPS/img_text/g6_1vtam.htmPK >Al?~ y OEBPS/img_text/g8_1vtam.htmPK >AgW OEBPS/img_text/g6_1sna.htmPK >AR M OEBPS/img_text/g1_1trms.htmPK >A&s n OEBPS/img_text/g7_1vtam.htmPK >ATgr m P OEBPS/img_text/g1_2arch.htmPK >Aa OEBPS/ch12.htmPK >AGq
OEBPS/toc.ncxPK >A $ $
l OEBPS/ch5.htmPK >As}## # OEBPS/content.opfPK >AP
OEBPS/lof.htmPK >A_
OEBPS/dcommon/prodbig.gifPK >AY@
[
OEBPS/dcommon/doclib.gifPK >Aqz@BX N
OEBPS/dcommon/oracle-logo.jpgPK >A S
OEBPS/dcommon/contbig.gifPK >A >
OEBPS/dcommon/darbbook.cssPK >AMά" " !
OEBPS/dcommon/O_signature_clr.JPGPK >APz
OEBPS/dcommon/feedbck2.gifPK >A-
OEBPS/dcommon/feedback.gifPK >Aː5 #
OEBPS/dcommon/booklist.gifPK >AN 6 1
OEBPS/dcommon/cpyr.htmPK >A!:3 .
OEBPS/dcommon/masterix.gifPK >AeӺ1 , {
OEBPS/dcommon/doccd.cssPK >A7
OEBPS/dcommon/larrow.gifPK >A#
OEBPS/dcommon/indxicon.gifPK >AS' "
OEBPS/dcommon/leftnav.gifPK >Ahu,
OEBPS/dcommon/uarrow.gifPK >Al-O J
OEBPS/dcommon/oracle.gifPK >A( OEBPS/dcommon/index.gifPK >AGC OEBPS/dcommon/bookbig.gifPK >AJV^ OEBPS/dcommon/rarrow.gifPK >A枰p k " OEBPS/dcommon/mix.gifPK >Ao"nR
M
OEBPS/dcommon/doccd_epub.jsPK >Av
I
p" OEBPS/dcommon/toc.gifPK >A
r~$ # OEBPS/dcommon/topnav.gifPK >A1F A '% OEBPS/dcommon/prodicon.gifPK >A3(
#
( OEBPS/dcommon/bp_layout.cssPK >A x[? : &6 OEBPS/dcommon/bookicon.gifPK >Ap*c ^ ; OEBPS/dcommon/conticon.gifPK >Aʍ X? OEBPS/dcommon/blafdoc.cssPK >A+ & WV OEBPS/dcommon/rightnav.gifPK >Aj e8 8 W OEBPS/dcommon/oracle-small.JPGPK >Aއ{& ! OEBPS/dcommon/help.gifPK >Aѩe e
u OEBPS/toc.htmPK >A8_EȊ OEBPS/ch13.htmPK >ABD
r OEBPS/apc.htmPK >A MT HT
m OEBPS/ch7.htmPK >AM
?
OEBPS/lot.htmPK >Astƕ[ [ HG
OEBPS/ch14.htmPK J J ;
