The following sections detail how to configure the OLTP.
If your communications protocol is SNA: proceed to Section 7.1, "Configuring the OLTP for Your SNA Environment".
If your communications protocol is TCP/IP: proceed to Section 7.2, "Configuring the OLTP for Your TCP/IP Environment".
|
Note: On a gateway using TCP/IP support for IMS Connect, you must specifyEDIT=ULC in the IMS TRANSACT macro if you need input case sensitivity. When using SNA support, you need not specify EDIT=ULC in the IMS TRANSACT macro. |
The steps for configuring your 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 suitable to your OLTP from the following sections:
|
Note: You need only perform the configuration steps for an OLTP if this is a first-time configuration for that OLTP. |
Configuring 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 Server 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 your 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:
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 Windows. 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.
If your OLTP is IMS/TM, then perform the following steps to configure IMS/TM and z/OS for communication with the gateway:
Configure the IMS system for use with APPC.
Configure MVS VTAM for the SNA APPC connection to Windows. 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:
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 a 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.
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 Windows. 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 dataset (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 suitable for the device type on which it resides. Approximately two tracks of 3390Ā disk space are required with one directory block. Oracle suggests naming this partitioned dataset (PDS) ORAPGA.APPCMVS.SAMPLIB.
Using the 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 is 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 is 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 dataset. Ensure that you change the dataset name in the JCL to match the name of the z/OS PDS allocated in StepĀ 3.
The APPC/MVS configuration is now complete.
Now that you have completed configuration of the network on a gateway using the SNA protocol, proceed to Chapter 8, "Gateway Configuration Using SNA Communication Protocol".
If you wish to configure commit-confirm, then instructions for this configuration can be found in Section 8.8, "Configuring Commit-Confirm".
These are the steps for configuring the 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 the IMS system.
Configure IMS Connect.
For information on how to configure IMS Connect, refer to the IBM IMS Connect Guide and Reference.
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:
Add the statements in the imsgen.asm file to the 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 a 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.
At this point, proceed to Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol" to complete configuration of the gateway and its components.
This chapter describes the system requirements of the gateway. It contains the following sections:
The hardware requirements for this release of the gateway on Microsoft Windows are described in the following sections.
Refer to the Oracle Database Installation Guide for Microsoft Windows for Microsoft Windows and to the certification matrix on My Oracle Support for the most up-to-date list of certified hardware platforms and operating system version requirements to operate the gateway for your system. The My Oracle Support Web site can be found at:
The Oracle Database Gateway for APPC requires an Intel or 100% compatible personal computer based on a Pentium processor that can run Microsoft Windows 2000 and higher.
For most installations, Oracle recommends a minimum of 256 MB of real memory for the system running the Oracle Database Gateway for APPC.
Each concurrent use of the gateway requires a minimum of 10 MB.
The following factors affect the virtual memory requirements of the gateway server process:
number of concurrent gateway connections opened by each user;
number of data items being transferred between the gateway and the RTP;
additional factors such as configured network buffer size;
the Oracle Net protocol adapters that were included during the gateway installation.
The gateway requires any network attachment supported by either the SNA Server for your platform or the TCP/IP Networking Facility for TCP/IP communication.
However, if you are using solely the new TCP/IP support for IMS Connect feature, you will not need an SNA package. The Windows operating system comes with TCP/IP installed, you will need to configure it.
The system software configuration described in these requirements 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 for Microsoft Windows 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 Windows Intel system. The My Oracle Support Web site can be found at:
A Microsoft Host Integration Server 2000 is required, or IBM Communication Server V6.1.1 (or higher) for Windows. In this document, either of these communications servers will be referred to generically as SNA Server.
|
Note: If you choose to use TCP/IP support for IMS Connect as your communications protocol, then you will not need to use an SNA Server. Your operating system comes with a TCP/IP protocol automatically installed. If you choose to use the TCP/IP protocol, you will need to configure it to work properly with the gateway then instructions for doing so are located in Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol". |
The Microsoft Windows platform requires that the Oracle database which is to act as the Oracle database be up to date with the latest patch set for supported Oracle database releases.
Oracle Net is automatically installed on the system where the Oracle database is installed and on the system where the gateway is installed. Refer to Chapter 5, "Configuring Your Oracle Network" in this guide for configuration information. Additionally, you may refer to the Oracle Database Net Services Administrator's Guide.
In addition to the other software requirements of the gateway and your particular platform, 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, and z/OS.
Important: For a list of known restrictions, read the "Known Restrictions" section before proceeding with installation of the gateway.
IMS/TM: Release 7.1 or later is required, as well as any APARs (patches) listed in the IBM IMS Connect Guide and Reference.
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's 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 the security scheme, you must understand the existing security requirements and expectations in the environment. Because you are enabling application access to different databases on different systems, you must merge multiple security cultures. When developing your security scheme, the most stringent security requirements prevail. When you connect 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 (RTP) 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 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.
An application must connect to an Oracle database before using that gateway. The type of logon authentication that you use determines the resulting Oracle userĀ ID and can affect gateway operation.
Two basic types of authentication are available:
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 server's underlying 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 to such a userĀ ID, the application supplies a slash ( / ) for a userĀ ID and does not supply a password.
To perform operating system authentication, the server determines the requester's 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 were authenticated when they logged 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 multi-threaded server configurations. Refer to your Windows Oracle database documentation and Oracle Database Net Services Administrator's Guide to determine the availability of this feature in your configuration.
For more information about authenticating application logons, refer to the Oracle Database Administrator's Guide.
The following sections discuss database links for users of the gateway employing either TCP/IP or SNA communications protocols.
The first point of control for a database link is whether 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. The Oracle database makes no distinction as to the type of use (such as read-only and update or write) or which remote objects can be accessed. These distinctions are the responsibility of the OLTP that is accessed.
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 user's 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 user's Oracle userĀ ID and password are sent to the gateway when the connection is opened. If the user logs on to the Oracle database with operating system authentication, then the gateway receives no userĀ ID or password from the 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.
For more information about database links, refer to the Oracle Database Administrator's Guide.
The information in this section 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 Windows' Logical Unit (LU) and the OLTP LU.
APPC support for the Windows platform is provided by the SNA Server (Microsoft Host Integration Server or IBM Communication Server v6.1.1 or higher).
SNA and its various access method implementations, including VTAM and the SNA Server, 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 Microsoft Windows' SNA profiles and in similar parameter structures in the OLTP to be accessed. Refer to the suitable communications software product documentation for detailed information about this subject.
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.
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.
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.
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 RTP 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: Because 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 communicate with IMS Connect. Use thepg4tcpmap 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 Microsoft Windows and in similar parameter structures in the OLTP to be accessed.
The PGA_SECURITY_TYPE parameter of the gateway initialization file allows you to specify the security conduct for the conversation that is allocated by the gateway for OLTP. Refer to Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol".
If you specify PGA_SECURITY_TYPE=NONE, then the gateway performs no processing of the client userĀ ID and password.
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 communicates with IMS Connect.
|
Important: You must specify your RACF group name through thepg4tcpmap 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. |
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 Heterogenous Services making it possible to encrypt parameters values. This is done through the dg4pwd utility.
|
See Also: Refer to Oracle Database Heterogeneous Connectivity User's Guide for more information about this utility |
Installation and Configuration Guide
11g Release 2 (11.2) for Microsoft Windows
E12079-02
February 2010
Oracle Database Gateway for APPC Installation and Configuration Guide, 11g Release 2 (11.2) for Microsoft Windows
E12079-02
Copyright Ā© 1996, 2010,Ā Oracle and/or its affiliates. All rights reserved.
Primary Author: Ā Maitreyee Chaliha
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.
The following worksheet 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). Use the 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 |
|---|---|---|
|
|
for: gateway's Oracle Home |
ĀĀĀĀĀĀĀĀĀĀĀĀĀĀĀ _______________________________ |
|
|
for: gateway's system ID |
_______________________________ |
|
Any Security Options Needed |
for: SNA remote LU properties options |
_______________________________ |
|
Suitable Name for Each Side Information Profile |
for: SNA creating CPI-C symbolic destination names (side information profiles), general information |
_______________________________ |
|
Suitable 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, |
_______________________________ |
|
IP Address |
for: Configuring TCP/IP support for IMS Connect, |
_______________________________ |
|
IMS Connect Port Number |
for: Configuring TCP/IP support for IMS Connect, |
_______________________________ |
|
Conversational Protocol (Y/N) |
for: Configuring TCP/IP support for IMS Connect, |
_______________________________ |
|
Timer choice: a) .25 b) .01 to .25 c) Does not exist d) Receives wait |
for: Configuring TCP/IP support for IMS Connect, |
_______________________________ |
|
Socket Connection Type Choice: a) transaction b) persistent c) nonpersistent |
for: Configuring TCP/IP support for IMS Connect, |
______________________________ |
|
IMS Client ID Name |
for: Configuring TCP/IP support for IMS Connect, |
______________________________ |
|
IMS Commit Mode Choice: a) 0 b) 1 |
for: Configuring TCP/IP support for IMS Connect, |
_____________________________ |
|
IMS Destination ID, datastore name |
for: Configuring TCP/IP support for IMS Connect, |
_____________________________ |
|
|
for: Configuring TCP/IP support for IMS Connect, |
______________________________ |
|
RACF Group Name |
for: Configuring TCP/IP support for IMS Connect, |
_____________________________ |
|
|
for: Configuring TCP/IP support for IMS Connect, |
_____________________________ |
|
|
for: Configuring TCP/IP support for IMS Connect, |
_____________________________ |
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 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 Remote Procedural Call (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. Thus, the gateway uses existing transactions with little or no programming effort on the remote host.
For gateways using SNA:
The use of a generic and standard protocol, APPC, allows the gateway to access a multitude of systems. The gateway can communicate with virtually any APPC-enabled system, including IBM Corporation's CICS on any platform and IBM Corporation's 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.
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, giving users a choice of whether to use the SNA or TCP/IP communication protocol. IMS Connect is an IBM product which allows 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. Related to this new feature of the gateway is:
The pg4tcpmap tool. This release of the gateway includes a new tool whose purpose is to map the information from your side profile name to TCP/IP and IMS Connect. For more information about the gateway mapping tool, refer to ChapterĀ 6, of the Oracle Database Gateway for APPC User's Guide, and to Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol" in this guide.
The gateway is optimized so that remote execution of a program is achieved with minimum network traffic. The interface to the gateway is an optimized PL/SQL stored procedure specification (called the TIP or transaction interface package) precompiled in the Oracle database . Because there are no additional software layers on the remote host system, overhead occurs only when the program processes.
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.
Users calling applications that execute a remote transaction program are unaware that a request is sent to a host.
You can use the gateway to interface with existing procedural logic or to integrate new procedural logic into an Oracle database environment.
The integration of the Oracle database with the gateway enables the gateway 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 transfer updates and Oracle database updates to be performed in a coordinated fashion.
The gateway supports any tool or application that supports PL/SQL.
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.
The gateway provides site autonomy, allowing you to do such things as authenticate users. It also provides role-based security compatible with any security package running on the mainframe computer.
The following terms and definitions are used throughout this guide. Refer to Appendix C, "Gateway Terminology" for a more elaborate list of terms and definitions pertaining to the gateway, its components and functions.
This is any Oracle database instance that communicates with the gateway for purposes of performing remote procedural calls to execute remote transaction programs (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.
Online Transaction Processor (OLTP) is any of a number of online transaction processors available from other vendors, including CICS Transaction Server for z/OS, IMS/TM, and z/OS
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.
Procedural Gateway Data Dictionary (PG DD) is a repository of remote host transaction (RHT) definitions and data definitions. PGAU accesses definitions in the Data Dictionary (PGĀ DD) when generating TIPs. The PG DD has datatype dependencies because it supports the PGAU and is not intended to be directly accessed by the customer. Refer to Appendix A, "Database Gateway for APPC Data Dictionary" in the Oracle Database Gateway for APPC User's Guide for a list of PG DD tables.
Remote Procedural Call (RPC) is a programming call that executes program logic on one system in response to a request from another system. Refer to "Gateway Term Definitions" for more information, and refer to Appendix C, "Gateway RPC Interface" in the Oracle Database Gateway for APPC User's Guide as well.
A remote transaction program (RTP) 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 RTP through the gateway, you must use RPC to execute a PL/SQL program to call the gateway functions.
A Transaction Interface Package (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 or UTL_PG functions.
Figure 1-1, "Relationship of Gateway and Oracle Database on Windows" illustrates where the terminology discussed in the preceding sections apply within the gateway's architecture.
Figure 1-1 Relationship of Gateway and Oracle Database on Windows
The architecture of Oracle Database Gateway for APPC consists of several components:
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
The OLTP must be accessible from the gateway using the SNA or TCP/IP communication protocol. Multiple Oracle database s can access the same gateway. A single system gateway installation can be configured to access more than one OLTP.
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 database s 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, then 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 Microsoft Windows. It has the following components:
a home directory, similar to the one associated with an Oracle instance's ORACLE_HOME environment variable;
a system identifier, identified as sid or ORACLE_SID;
an initialization parameter file, similar to the Oracle database 's 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 product. Each Oracle database user session that accesses a particular gateway creates an independent process on Windows, which, in turn, runs the gateway server and executes either the SNA or TCP/IP functions to communicate with an OLTP.
All of the communication between the user or client program and the gateway is handled through a 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 RTP;
calls the gateway packages that handle the communications for starting the conversation, exchanging data, and terminating the conversation;
handles all datatype conversions between PL/SQL datatypes and the target program datatypes.
The 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
The Oracle Database Gateway for APPC provides a set of functions that are invoked by the client through remote procedural call (RPC). These functions direct the gateway to initiate, transfer data with, and terminate RTPs running under an OLTP on another system.
Table 1-1 lists the RPC 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 |
|---|---|---|---|
|
|
|
|
Initiate program |
|
|
|
|
Exchange data |
|
|
|
|
Terminate program |
The following sections describe how the RPC functions perform on gateways using SNA or TCP/IP communication protocols.
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. Future calls to the target program made by PGAXFER and PGATERM use the socket file descriptor as an input parameter.
Refer to Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol" in this guide, and to Chapter 6 in the Oracle Database Gateway for APPC User's Guide, for more information about the function and use of the pg4tcpmap tool.
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's PL/SQL datatypes to RAW before sending the buffer to the gateway. It is also responsible for converting RAW to the PL/SQL datatypes before returning the results to the application.
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.
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 executed 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 RTP.
Refer to "Remote Host Transaction Types" in ChapterĀ 4, "Client Application Development" of the Oracle Database Gateway for APPC User's Guide for more information about transaction types.
The following list demonstrates the power of the Oracle Database Gateway for APPC:
You can initiate a CICS transaction on the mainframe to retrieve data from a VSAM file for a PC application.
You can modify and monitor the operation of a remote process control computer.
You can initiate an IMS/TM transaction that executes static SQL in DB2.
You can initiate a CICS transaction that returns a large number of records in a single call.
The Oracle Database Gateway for APPC using TCP/IP for IMS Connect supports three types of transaction socket connections:
The socket connection lasts across a single transaction.
The socket connection lasts across multiple transactions.
The socket connection lasts across a single exchange consisting of one input and one output.
|
Note: Do not use the nonpersistent socket type if you plan on implementing conversational transactions because multiple connects and disconnects will occur. |
Refer to the section about pg4tcpmap commands in Chapter 6 of the Oracle Database Gateway for APPC User's Guide and to Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol" in this guide for more information about how to enter these parameters.
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.
The following topics in this chapter describe how to install and configure the Oracle Database Gateway for APPC:
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 of the configuration actions on the OLTP might require you to restart the OLTP. In preparation for this, have your host system programmer or DBA review the instructions for your OLTP to allow for any necessary preparations.
To install and configure the gateway with a single Oracle database and a single OLTP, perform the procedures described in this chapter.
|
Note: If your gateway uses the SNA communication protocol, then you will follow the instructions for installation and configuration in this chapter, in Chapter 5, "Configuring Your Oracle Network" and in Chapter 8, "Gateway Configuration Using SNA Communication Protocol".If your gateway uses the TCP/IP communication protocol, then you will follow the instructions for installation and configuration in this chapter, in Chapter 5, "Configuring Your Oracle Network" and in Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol". |
If you have an earlier version of the Oracle Database Gateway for APPC installed on your system, then you may be upgrading or migrating to the current release. A gateway upgrade represents a minor software upgrade within a release, (for example, moving from Release 9.0 to Release 9.2.0) a gateway migration represents a significant change from one version number to another, (for example, migrating from Release 9.0 to 10.2).
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 will need to carry out specific tasks before you can install Release 11.2 of the Oracle Database Gateway for APPC.
After reading this section, you will need to read Chapter 11, "Migration from Existing Gateways" to determine the specific actions you must take 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 specific material related to migration of the gateway in Chapter 11, "Migration from Existing Gateways".
If you are installing for the first time, then begin with "Performing Preinstallation Procedures".
Perform the following steps to prepare for upgrading the Oracle Database Gateway for APPC to current versions:
Make backups of altered PGA shipped files.
Remove or rename any old gateway directories.
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 DD contains all of its earlier entries without modification. New PGAU control information has been 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, due to changes in the following:
PL/SQL compatibility
gateway server RPC interface
UTL_PG interface
TCP/IP only: If you have existing TIPs that were generated previously on a gateway using the SNA communication protocol and you want to use 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 due to the fact that 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.
Before you install the gateway, perform the following preinstallation procedures:
Ensure that your system meets all the hardware and software requirements specified in Chapter 3, "System Requirements".
Ensure that your security requirements are met.
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 Chapter D, "Configuration Worksheet".
Decide on an SID (system identifier) for your gateway. This SID is used in Section 8.7, "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 Server required for your platform. Refer to Chapter 6, " Configuring the SNA Communication Package on Windows" for more information about setting up and configuring SNA for Windows.
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 for Microsoft Windows
You can install the gateway in either 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.
For general information about installing Oracle products and how to use the Oracle Universal Installer, refer to the Oracle Database Installation Guide for Microsoft Windows and perform all necessary tasks there first.
If your server release is different than your gateway release, then 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.
If you wish to install the gateway in the same Oracle home as the Oracle database , then the release number of both products must be the same.
Logon to your Windows system as a member of the Administrators group. If you are not currently a DBA user, then contact your system administrator to create a DBA login userĀ ID. Refer to the Oracle Database Installation Guide for Microsoft Windows for login information.
If you are installing the gateway for the first time, then ensure that there is enough space on the disk where the gateway will reside, as specified in"Disk Space Requirements".
Before beginning the gateway installation process, you must stop all Oracle services that are currently running. Follow these steps:
Click Start, then Settings, then Control Panel.
Select Services. A list of all Windows services appears.
Select an Oracle service (those services begin with Oracle).
Click Stop.
Continue to select and stop Oracle services until all active Oracle services are stopped.
Verify that the drive is assigned to the logical drive you selected and that you can access files on the installation media.
|
Note: The installation steps that follow assume that the installation media location is mapped to the D: drive. |
The installation media package contains the Oracle Database Gateway for APPC and the Oracle Universal Installer.
To start the Oracle Universal Installer, run setup.exe:
From the Start Menu, select Run.
Enter the path of the executable file name. For example:
D:\Disk1\setup.exe
|
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 to use the Oracle Universal Installer to install the gateway on your platform.
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 Windows 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 Home Details |
a. Specify the name of the installation. Specify the full path where you want to install the product 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. (Note that you may also choose to select other products to install besides the Oracle Database Gateway for APPC). 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 Configutration, 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 Yes |
|
Oracle Universal Installer: End of Installation |
Click Finish |
|
Exit |
Click Exit |
Your gateway is now installed.
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 C:\Program Files\Oracle\Inventory\logs directory.
The default file name is InstallActionsYYYY-MM-DD_HH-mm-SS-AM/PM.log, where:
YYYY is year;MM is monthDD is dayHH is hourmm is minuteSS is secondsAM/PM is daytime or eveningEach of these variables in the log file name represents the date and time the product was installed.
|
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 the configuration of the gateway. |
This chapter describes how to remove Oracle Database Gateway from an Oracle home directory. It contains information about the following topics:
he Deinstallation Tool (deinstall) is available in the installation media before installation, and is available in Oracle home directories after installation. It is located in ORACLE_HOME\deinstall.
The deinstall command stops Oracle software, and removes Oracle software and configuration files on the operating system.
The script 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 noninteractive mode. This option requires a properties file that contains the configuration values for the Oracle home that is being deinstalled or deconfigured.
To create a properties file and provide the required parameters, see the template file deinstall.rsp.tmpl, located in the response folder. If you prefer, instead of using the template file, you can generate a properties file by using the -checkonly option to have deconfig discover information from the Oracle home that you want to deinstall and deconfigure. The tool will generate the properties file, which you can then use with the -silent option.
-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.
-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.
-paramfile complete 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\response
From a unzipped archive file from OTN: ziplocation\response
After installation from the installed Oracle home: ORACLE_HOME\deinstall\response
-params [name1=value name 2=value name3=value . . .]
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.
-o complete path of directory for saving files
Use this flag to provide a path other than the default location where the properties file is saved. The default location is \response\deinstall.rsp.tmpl.
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 an 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 optional flags
Complete the following procedure to remove Oracle software:
Log in as a member of the Administrators group.
Run the deinstall command, providing information about the Oracle System Identifier (SID), when prompted.
The 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 Microsoft Windows can be provided by using either of the following tools:
Microsoft Host Integration Server 2000(HIS), or
IBM Communications Server v6.1.1 (or higher).
Read this chapter to learn how to configure the SNA Server on a Windows system to run the Oracle Database Gateway for APPC, using either a Microsoft Host Integration Server or IBM Communications Server.
This chapter contains the following sections:
Creating SNA Server Definitions on Microsoft Host Integration Server
Creating IBM Communications Server Definitions for the Gateway
When a Remote Procedure Call (RPC) request to start a remote transaction program (RTP) 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 Windows Logical Unit (LU) and the OLTP LU.
SNA and its various access method implementations (including HIS and IBM Communication Server and VTAM) 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 the Windows SNA Server definitions and in similar parameter structures in the OLTP to be accessed. Refer to suitable communications software product documentation for detailed information about this subject.
Many OLTPs provide options for manipulating the security conduct of an inbound (client) APPC session request. Refer to suitable OLTP documentation 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.
However, ATTACHSEC=LOCAL, ATTACHSEC=IDENTIFY, ATTACHSEC=VERIFY, and ATTACHSEC=MIXIDPE are fully supported by the gateway.
The following sections discuss general information about the SNA Server and how to configure a Microsoft Host Integration Server.
|
Note: If you are using the IBM Communication Server to configure your Windows system for the gateway, then proceed to Section 6.5, "Configuring an IBM Communications Server". |
Oracle recommends 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 with the same OLTP through the independent LU.
Dependent LUs support only a single active session. The CP (Control Point for the Node, which is SNA Server for Windows 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 no alterations to the Oracle Database Gateway for APPC configuration are needed, nor should any changes be needed to 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 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 any one 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 configuration entries, which define the additional dependent LUs on the Windows system. The TIP that initiates the conversation must specify the different Partner LU through a different Side Information Profile or by overriding the LU name. Refer to PGAU DEFINE TRANSACTION , SIDEPROFILE, and LUNAME parameters in Chapter 2, "Procedural Gateway Administration Utility," in the Oracle Database Gateway for APPC User's Guide.
The %ORACLE_HOME%\dg4appc\sna subdirectory contains a sample set of gateway SNA Server definitions created with the SNACFG command. The snacfg.ctl file contains sample definitions for SNA Server.
Before building the SNA Server definitions, examine the snacfg.ctl file to determine the definitions needed, their contents, and their inter-relationships. The file format is text-oriented, and each field of each definition is clearly labelled. You can print a copy of the file to use while working with your definitions in a Microsoft Host Integration Server (formerly SNA Server Manager) session.
Several types of SNA Server definitions are relevant to gateway APPC/LU6.2 operation. Each definition can be created and edited using a corresponding Microsoft Host Integration Server (formerly SNA Server Manager) menu.
The definitions relevant to the gateway are presented here in hierarchical order. 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 Windows HIS online documentation for a complete discussion of HIS definitions. This section provides an overview of HIS definitions in relation to the Oracle Database Gateway for APPC.
HIS definitions can be created and modified in two ways:
You can create the definitions using menus in the Microsoft Host Integration Server (formerly SNA Server Manager).
Using the Microsoft Host Integration Server is the recommended method for creating the definitions. You should be able to accept most of the defaults. The default values assigned to many of the fields in a new set of definitions are acceptable to the gateway.
Step through the tasks for creating SNA Server definitions in Section 6.4, "Creating SNA Server Definitions on Microsoft Host Integration Server".
Alternatively, you can install the definitions directly on your system using the SNACFG command.
For information on using the SNACFG command, refer to your vendor documentation.
If you use the SNACFG command method, then you must use Microsoft Host Integration Server (formerly SNA Server Manager) to review and modify the installed definitions. Because of configuration and naming differences, it is unlikely that they will work without modification.
Maintenance of SNA definitions is normally done by a user with Administrator authority. The following information is intended for the person creating SNA definitions for the gateway. You should have some knowledge of SNA before reading the following sections.
This section describes the process of creating your SNA definitions in the Microsoft Host Integration Server (formerly called the SNA Server Manager). All of the tasks described in this section are performed from within the Microsoft Host Integration Server.
Select the appropriate folder to ensure that definitions created are for that server. When HIS Manager is started, a dialog box appears.
Select the Servers folder under your local system and select the local SNA Server. From a list of services for that server, select the SNA Service.
You must install and configure a link service for SNA Server to use the network adapter installed in your workstation, as follows:
From the Insert menu, select Link Service.
From the Insert Link Service dialog box, select the Link Service you want to use from the selection list and click Add. For example, select DLC 802.2 Link Service and click Add.
Now, the Link Service Properties dialog box is displayed. Note that the contents of this dialog box vary depending on which link service was selected. In this example, the DLC 802.2 Link Service Properties dialog box is used.
Select the suitable network adapter from the Adapter drop-down menu and click OK. In the Insert Link Service dialog box, click Finish. The system now updates your network bindings.
You must create a connection definition to define the devices which HIS uses to perform SNA communication. From the Insert menu, select Connection. The Connection Properties dialog box appears.
Select the General tab. Enter a connection name. This is the name used by HIS to name the connection. This example names the connection TOKEN1. From the Link Service drop-down menu, select a link service for the connection. All other settings can be left set to their default values.
Select the Address tab in the Connection Properties box. Enter the Remote Network Address and the Remote SAP Address.
Now, select the System Identification tab. Under Local Node Name, enter the Network Name, Control Point Name, and Local Node ID.
Under Remote Node Name, enter the Network Name, Control Point Name, and optionally, the Remote Node ID. The XID Type should be set to Format 3.
Next, select the DLC tab in the Connection Properties box. In this example, the 802.2 DLC (Token Ring) is being used. For the 802.2 DLC, all of the defaults are usually acceptable. If you need to change any values, then do so now.
Now, all the connection properties are set. Click OK to continue.
You must create a local logical unit (LU) definition. The local LU definition describes the SNA LU through which the gateway communicates with OLTP systems.
From the Insert menu, select Local APPC LU. The Local LU Properties dialog box appears.
Select the General tab. Enter the LU Alias, Network Name, and LU Name. Ensure that the APPC SyncPoint Support box is not checked.
Select Advanced tab of the Local APPC LU Properties box. Check the Member of Default Outgoing Local APPC LU Pool check box. Set the LU 6.2 Type to Independent to allow parallel sessions.
Now, the Local LU properties are all set. Click OK to continue.
This definition describes an SNA mode entry to be used when establishing sessions between LUs. The mode defined here must match a mode defined on the target system.
From the Insert menu, select APPC Mode Definition. The APPC Mode Properties dialog box appears.
Select the General tab. Enter the Mode Name. The mode name that you specify must be defined to the OLTP communications software. Choose the mode name in addition to other mode parameters after consulting the person responsible for configuring the OLTP communications software.
Next, select the Limits tab. Enter the Parallel Session Limit, Minimum Contention Winner Limit, Partner Min Contention Winner Limit, and Automatic Activation Limit values.
The Parallel Session limit determines the maximum number of concurrent conversations allowed between the gateway instance and the OLTP. This equates to the maximum number of concurrently active RTP calls through the gateway instance.
Now, select the Characteristics tab. Enter the Pacing Send Count, Pacing Receive Count, Max Send RU Size, and Max Receive RU Size. For optimal performance, check the High Priority Mode check box.
The pacing and RU size parameters are performance-related and should be tuned to suit your application. For most installations, the values set in the example are sufficient.
After you finish entering the values called for in this box, all the APPC mode properties will be set. Click OK at the bottom of the box to continue.
This definition describes the SNA LU of the OLTP system with which the gateway communicates. You must create a remote LU definition for the remote OLTP system. Determine the link with which to associate the LU (in the example, it is TOKEN1). From the Insert menu, select APPC Remote LU. The Remote APPC LU Properties dialog box appears.
Select the General tab. Use the Connection drop-down menu to select the connection used to access this LU. Enter the LU Alias, Network Name, LU Name, and Uninterpreted LU Name. You should contact the person responsible for your SNA network to determine the correct LU and network names. Note that you can use the LU Alias to define a name known only to SNA Server, and that name can remain the same even if the remote LU name changes. This helps to reduce the amount of maintenance required when network changes occur.
Now, select the Options tab. Check the Supports Parallel Sessions check box. Use the Implicit Incoming Mode drop-down menu to select the mode. Set any security options you need.
Once you have filled in the suitable values in the Remote APPC LU Properties box, the APPC LU properties will be set. Click OK to continue.
When the Local and Remote Partner definitions and Mode definitions have been created, you can create CPI-C Symbolic Destination Names, also called side information. The side information is used to identify target OLTP systems to be accessed through the gateway. From the Insert menu, select APPC CPIC Symbolic Name. The CPIC Name Properties dialog box appears.
Select the General tab. Enter a Name for the side information. From the Mode Name drop-down list, select the suitable mode.
Now, select the Partner Information tab. Select Application TP and enter the TP name. If you plan to define one CPI-C Symbolic Destination Name for accessing multiple transaction programs at an OLTP, then you can enter a dummy TP Name at this time. The TP Name is overridden by the gateway at run time.
Enter the Partner LU Name Alias.
Click OK to save the side information.
Configuration of the Microsoft Host Integration Server is now complete. Proceed to "Testing the Connection".
If you are using IBM Communications Server as your SNA Server, then read the following sections to learn how to configure it to communicate with the Oracle Database Gateway for APPC.
Oracle recommends 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 with the same OLTP through the independent LU.
Dependent LUs support only a single active session. The CP (Control Point for the node, which is IBM Communications Server, 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 gateway LU is correctly defined, then no alterations to the Oracle Database Gateway for APPC configuration are needed, nor should any changes be needed to the gateway server.
The operational impact of dependent LUs is that the first client application can initiate a conversation through the 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 really 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 requires that additional dependent LUs be defined on the remote host, plus additional IBM Communication Server configuration entries, which define the additional dependent LUs on the host Windows 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.
Refer to PGAU DEFINE TRANSACTION, SIDEPROFILE, and LUNAME parameters in Chapter 2, "Procedural Gateway Administration Utility," in the Oracle Database Gateway for APPC User's Guide.
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 here in hierarchical order. 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. This section provides an overview of IBM Communications Server definitions in relation to the Oracle Database Gateway for APPC.
IBM Communications Server definitions are created using the SNA Node Configuration tool, while the actual 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 your SNA definitions for IBM Communications Server using the SNA Node Configuration tool. All the tasks described in this section are performed within SNA Node Configuration.
SNA Node Configuration will first ask you 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 will next prompt you for a configuration scenario.
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 the Control Point, Local Node ID, and Node Type information.
You can select Advanced tab options, depending on your SNA network configuration.
Click OK.
Configure Communication Devices next. Follow these instructions:
Click Devices.
Click Create.
Select the type of device to use for communication. The LAN type is typical for either Ethernet or Token Ring attached network devices.
Configure a LAN device next. Follow these instructions:
Select the Basic tab. Select the adapter to use and the Local SAP.
The other tabs provide options on network tuning parameters.
Click OK.
Configure Peer Connections next. Follow these instructions:
Click Peer Connections.
Click Create.
Define the Link Station next. Follow these instructions:
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.
Define the Adjacent Node next. Follow these instructions:
Select the Adjacent Node tab.
Enter the Adjacent CP name of the remote system and pick its CP type. You may 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.
Create Local LUs for this node next. Follow these instructions:
Click Local LU 6.2 LUs.
Click Create.
Define Local LUs next. Follow these instructions:
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.
Create remote Partner LUs next. Follow these instructions:
Click Partner LU 6.2 LUs.
Click Create.
Define Partner LUs next. Follow these instructions:
In the Basic tab, enter the name of the Remote or Partner LU, and, optionally, an alias.
Select the Fully Qualified CP from the Existing list.
You can examine the other tab for logical record limits and security support.
Click OK.
Before proceeding with the gateway configuration tasks, ensure that your connection is working. You can do this by using the Microsoft Host Integration Server (SNA Server Manager).
Figure 6-1 shows the relationship between SNA Server definitions and the VTAM definitions on the host.
Figure 6-1 Relationship Between SNA Server Definitions and Host VTAM
When you have finished configuring the SNA Server for your Windows system, proceed to Chapter 7, "Configuring the OLTP" to continue configuring the network.
This appendix lists and describes the parameters needed specifically 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:
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: Theinitsid.ora file contains both SNA and TCP/IP parameters. You will need to modify these files with the appropriate parameters. |
The Procedural Gateway Administration (PGA) parameters control the TCP/IP interface portion of the gateway.
PGA parameters are specified using the SET gateway 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 |
|---|---|
|
where:
NOTE: This parameter will be used for the | |
|
PGA transaction capability. The following are valid values:
| |
|
TCP/IP conversation security option. This controls what security parameters are sent to the OLTP. The following are valid values:
The default is For further information on these options, refer to Chapter 10, "Security Requirements". Important: You must specify your RACF group name through the If you have already loaded the table | |
|
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 There is no default value. | |
|
The Oracle password to be used by the gateway when connecting to the Oracle database specified by the There is no default value. | |
|
The Oracle userĀ ID to be used by the gateway when connecting to the Oracle database specified by the There is no default value. | |
|
PGA trace level. This controls tracing output written to The default isĀ 0, indicating no tracing. NOTE: This parameter will be used in the |
The following output illustrates the results from executing the pg4tcpmap tool when running TCP/IP for IMS Connect on the gateway. Refer to Section 9.8, "Loading the PGA_TCP_IMSC Table" of this guide and to Chapter 6 of the Oracle Database Gateway for APPC User's Guide for detailed information about the function and parameters of the pg4tcpmap tool.
Note that input in this sample is shown within brackets angle brackets (<>).
C:\oracle\bin\<pg4tcpmap> PG4TCPMAP: Release 11.2.0.1.0 - Production on Thu Jun 11 15:09:00 2009 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. 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.
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(COMMUNITY= TCP.world)
(Host = bay)
(PROTOCOL= TCP)
(Port= 2621)
)
(ADDRESS=
(COMMUNITY= TCP.world)
(Host = bay)
(PROTOCOL= TCP)
(Port= 2623)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PGA)
(ORACLE_HOME = C:\oracle\pga\11.2)
(PROGRAM = pg4t4ic)
)
)
ORA920 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = bay.us.oracle.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORA920.bay)
)
)
PGA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = bay)(PORT = 2623))
)
(CONNECT_DATA =
(SID = PGA)
)
(HS = OK)
)
The Oracle Database Gateway for APPC provides Oracle applications with seamless access to IBM mainframe data and services through Remote Procedure Call (RPC) processing.
Refer to the Oracle Database Installation Guide for Microsoft Windows and to the certification matrix on My Oracle Support for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site can be found 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 Windows operating system, SNA Server, the Database Gateways, PL/SQL and the Oracle database .
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.
The Oracle Database Gateway for APPC Installation and Configuration Guide for Microsoft Windows is included as a 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 may be referenced in this book:
In addition to the Oracle documentation, ensure that you have required documentation for your platform, for your operating system, and for your communications packages.
The following IBM documentation may be useful:
IMS Connect Guide and Reference
The title of the IBM publication was accurate at the time of the publication of this guide. Titles and structure of these documents are subject to change. For other operating system, SNA communication package, and TCP/IP package references, refer to the appropriate vendor documentation for your system.
Examples of input and output for the gateway and Oracle environment are shown in a special font:
C:\> mkdir \ORACLE\your_name
All output is shown as it appears. For input, the list of conventions and their meanings are as follows:
example text:Ā Words or phrases, such as mkdir and ORACLE, must be entered exactly as spelled and in the letter case shown. In this example, mkdir must be entered in lowercase letters and ORACLE in uppercase letters.
italic text:Ā Italicized uppercase or lowercase, such as your_name, indicates that you must substitute a word or phrase, such as the actual directory name.
BOLD text or bold italic TEXT:Ā Bold words or phrases refer to a file or directory structure, such as a directory, path, or fileĀ ID.
... :Ā Ellipses indicate that the preceding item can be repeated. You can enter an arbitrary number of similar items.
{ }:Ā Curly braces indicate that one of the enclosed arguments is required. Do not enter the braces themselves.
|:Ā Vertical lines separate choices.
[ ]:Ā Square brackets enclose optional clauses from which you can choose one or none. Do not enter the brackets themselves.
Other punctuation, such as commas, quotation marks or the pipe symbol (|) must be entered as shown unless otherwise specified. Directory names, fileĀ IDs and so on appear in the required letter case in examples. The same convention is used when these names appear in text, and the names are highlighted in bold. The use of italics indicates that those portions of a fileĀ ID that appear in italics can vary.
Gateway commands, fileĀ IDs reserved words, MS-DOS commands, keywords and environment variables appear in uppercase in examples and text. Reserved words must always be entered as shown; they have reserved meanings within the Oracle system.
SQL*Plus Prompts
The SQL*Plus prompt, SQL>, appears in SQL statement and SQL*Plus command examples. Enter your response at the prompt. Do not enter the text of the prompt, SQL>, in your response.
MS-DOS Prompts
The MS-DOS prompt, C:\>, appears in MS-DOS command examples. Enter your response at the prompt. Do not enter the text of the prompt, C:\>, in your response.
PGAU Prompts
The PGAU prompt, PGAU>, appears in PGAU command examples. Enter your response at the prompt. Do not enter the text of the prompt, PGAU>, in your response.
Directory Names
Throughout this document, there are references to the directories in which product-related files reside. %ORACLE_HOME% is used to represent the Oracle home directory. This is the default location for Oracle products. If you have installed into a location other than %ORACLE_HOME%, replace all references to %ORACLE_HOME% with the drive and path specification you have used.
}9Tšh0?½/šĮ„MĄ Šhm Šlę)0lš[°>M GšÓ>½RÖ{ÓhÓ3
æ ÖnŻø,$t °8ĄŠ $ :š`©6T' .@
0°ė 1`o©¾üÖnmĻ*Ļ Ó9}³UQ 9@ WŚ P?ĄTPįA0 2° o°1ph¬z<š’¾żŪĄ ÜĀ=ÜÄ]ÜĘ}ÜČÜČmķė¾ÜÖÖV[]PŅišb@Ņ}cjŖV)ądĄŌRĶf\0/°6ČŠ&-_PŅtPšŁ{K°ßüŻßžżß ą>ą^ą^ą'Š“¶Ö(ÜÖ0æ į>į^į~įį¾į į[ĄĶŁ
ņH@&~ā=ā*¾ā,Žā(^+>(ŠMwŲ ć:¾ć<Žć>žć@ äB>äD ä ¾XĻ]Ó#! PB`R>åT^åV~åXåZ¾å\ŽåX^g?¼ZĆ¼Öń`p’<=
E µŲ äŪ¼ä“v D Ąz¾ē|Žē~žē č>č^čj° c:
^sé>éī„Hpéé¾éŽéé„ Né%š“²nNurÉdÜ“ ±źŁ S;Żō¹b0Y ¼Žė¾.»žėĀ>ģÄ^ģĘ.ģĮnģi
7Ŗ¾źłJĢ°«²Ī±ż¼ÆsąPÜŽķŽ^²šķā>īä^īę.īįnīķóģn ķ÷<ķ²
Ö®ÓāķI ś¾ļüŽļžžļ š?š?ģīģ×,ó^ š~Łņ¾š/’opŻč ųNšńæń’nšĶŽ3īµ
Ʊ0[®ó^ļ"~ļ^ļ ßņ.’ņśīńķš
ńskuÜ ®%Oķ«ņŌ}µóB?ō/ó_Ā
oó#o±;oóWė!žóŲ¾ņI°XõZæõ\ßõ^’õY
Poō OóNĻšIĖąŻüši_æ¼q Oõ90^Ņ|ß÷~’÷ķ]ĄŪ^ōöH_óæō ĶääŹónīóō Hąšļp`š_¢ųé ś¢/( nxpdš2!æ“OÓunņÕõ6+õ0HŠ’ČGŻū/@[`ś_šZ L UüŹæüĢßüĪ’üČ_p[šM =½Õ[}Ōsąvåśh’ö7’ÆīųöoµuģßžYŠc jcš UZu|’ų’śæ’üjL#LxV_%tOWW-W4*-<~¤„„'Ŗ«¬®Æ ¦„< 7°¼½¾®p'
£¶~<#æĖĢĶŖ ÅĘ$ !!¼ecn%a##uZčéźėģķīļčćä^_QHyyz[R={1 E*DØiŠ@
L~č°iG ’(^¢A””9É¢E
®(S^
6¬$2e*cŹĢMZIkŲ ČNpP <Ó
^h&(9X0
U}ļVą`° 7š7õh
1sn ©aHØaŠ >å)`6ą>ąKĄ>!°|ńä0@Qč 7°fĄ 6` pF1p š)` Ąuų7Tą éĄ#ą4’bt` š~ńĄļ ā ā `,³Ä W \ Šų°H`] {@ āa WVHš>p' „Ęčų3Ų1Ø8Čą P! ŠKąp)ōi@ta H`°#įB` G 6@°MĄĒ (2ęS+ĆK° 7°9 .0>Š H
` <ž±Æį)@ 19gŠ6 :)tfŠ !ć@`?As` ± N Fē’yn° =5°wPNx! ąCpwĄ > yĄ: 9py)~YpDł4¼“WĄoe `% NąN p 3 w` Eą83qČppŠ8 ;0w
Aā`A&Q@>ąS±F)P-ąp`ķqC WW!*ZzqšEh.7æ8éÉ$&ĪQ Vp;p\ y «V 8ŠPā”
±2pqpąyJ’°N°CPķ07 §%ą8 : "ZÜAw°`·Ń y 6'p pž± Üs4āĄp|ą?I:ėéGķ7
u:Ą) 6jš:hĄ pŗ5©}ą"-P>`Ķ ÖB\ą&j pb`ļø4cSAs“³yÖ¤”w£jO„J9ĢŖ>ŻŹOĪź>ŠZ6Ņś=Ōŗ/ÖzF±¤ąŠ¤JńMÆX® 4®S®t®!®ź*{ŁJRŪ>ņŖO[ōEö*;ų*DśZ4üŚÆ?Į®ßą®ß’|ß°§ļŠ§c°źØ|ć Ŗ ė
ė
'5 Qąl7pŠMøM p id
ŠŁ3
Ū3kH +Z ;G
6;²_ųÆR°KT°%Š` °@pĪ¹CPGp p- oÄ =` ņy
=«ū
ŖWe²'@t[·v{·x·z»·|Ū·~«·Py*%{L HKH ą ąKš£b¤TQk¶K\?LA[[CYEĖ8ü
W°¢HŗŖ»ŗ¬Ūŗ®ūŗ°»²Ėŗū«“Uøų4°o ’ tvpA v ŪyTš÷{]ėO\”KZ£k;üJ
pŽū½ą¾ā;¾ä[¾ę{¾čK¾J`|»«„»&’ém7 AP@Śsµ7 ąŲŃ«^ÓŪ` L!×+|ĄōWp«%SBš/ū
' rS Š° 7 CĄ·±\“Āwp¼tQ”¹R9!¹FĮĄzĀ
Õ Āņ 42ĮŪ²Į®ŠĮÆH@iI;P:ųb0ÅŠ hf4ü$@0Pb<Ęd\Ęf|Ęh’Ęj¼Ęzp°Ęp Ēf V
Š rĒz¼ĒkÜ %Ē|<Čr W°jA Cl2E¬Įīė[šKUšZ aš 6`W ų Hąmp¶é`.3¬ÜŹ®üŹ° Ė²<Ė“\Ė3p°Źµ¼Ė¼üŹ3 ŠĖĀ<ĢÄĢĖæ| ĖżĢĘ,'°Č%ÓČGüČŃÉ5ÉP<Śxą¼u Tą ŁÅH{Īű6Ņ©Łs
wš
ŠM0Ķr
gP?ß@Ķķ¹|,\ĪźlĮf“?j`N
£ {ą’ °= ycp`Äp ž|» -X] Ø|Š(M* µĪ`<ó` 0
10
`Äduvsčą0@=ü¹Kēw =Š |`ŃwŠ`3>Por%
kš MFA ō{É -ŅSĶUŠč
Ö)½ÖÆŠp± Ą ?PaāŠ0 H
07P pü fFp5ąCprjHŠ% Š2 i H> {ąMŠ Hp @Ib:ÖPeĶäeÖĄ„ÖfŪlŪ£ąÖą’ŹŹš: ;° lPĀhšp¦Ųß HĄ
H {š|š[ąŁC@q20 `yQĄĮÉ! Ū#Żk%- 'ŪĶŪĄ 1¹š$Ń p@?]ąŚ0Š 0Š¤DŻpppæćįv2šLn ŻpP Wš$! Æ&Ē\Š =,Ößä¶ß½ŪžŻćŠ,Ä
Ķjš W¬ i °ØxJšTpnšńpŲÓF”c[Š nĢAą„½l„’ä'ps ap,ō [ _ 5.°½'HÜ
Jģ
ė
żķć# ąĘSŲąäOn 8Ś(WŠŚTp ą&lĮ ¤ H°W h WĄ NP3Nš!°¢ ĶKBąa»&|I6^Ķ8Nu:nX>ģļ@č#0Ńrå 0 m@.ߣé głüi0 B eŪB šmšŽ.ąEĄ
sP ;Š0oŠvĮśŚ7^ÖĮ $ ° pqpV °NPypv° špQ0V{ŗ× { N,É«WŹ¢¬ Š)PVP10 ą.śJ ¼e0’¼ 0ng½w7£BQf Ą ²Ć<ģ q Y`² < =Ė ”
wš nv`q0K°!
ač/=0© X# ;p6ū7Ą»ń @'` °Č:°ń6W@` f@Ū;JeP ę[Vš H] `@)a e wÉsPü ,F-` K@;` iłzgP7@Æ «1`d0Š2p(m ĒŠ Ą}š'ü’Ā6j
Y É÷bĄøŚ¼ĶÜløošĶbzy5j ,ČML OL QL S¼b! @
š;<@ d #`»m°o|w7@Xp®¼l` m÷apd=`Kąe«üv` ćČJHpt9p]ąčk¼Ė<° t`ż¹6H0ī7vP#6Q-p Č,°Ų 0üŹz3p7ąĒ >(@ 7šlĄVP@Ė Ī»`9
:Ķ¢`jx nżÖp ×r=×t]×vķÖ@k’ Ī³°Ī³ŠĪ³ ztp1b#p} 2P
ĄG`ÆźŲzn@ÆŠŃ¶p ż{plż«K Š
ąepĀ ąMP ż=P ` gąNą«] Šq`7PĖš 7PH`G0ČN`'pA @[PÕH P Ō ŌøLN}H )£6ÜŠ ?`Ü_]Ė% pąeim§¬ĄvQą~ąr±@¬=RŅ¦ +įŚ ą[P °įe°NpĆ+i·
K’ } Mą®:Ą0p©.žā0 ć2>ć4^ć6~ć7ī?šŁ”}7°3 æ, B@½^@3³, Čp pp =š @8čļ 2ąnh«mpŁNp^ ž Žū :)i0?I³ä}MżŌ0 šŪ ąæ³x Ē@ĮÖP<Ą <š ¾Ōš1oĪ>#^#.Å>C@²s°7<qPtd*¦øėŗ¾ė¼Žė¾žėĄ ģĀ.ģ° ŚthŪåKH@ ɼ’±a]pJ®ŹµĻhPÕ; `H*^Fopß®Ž«}L iŻÜ«« ēÖ[P¾ poKfČ0é@uK=čPVą%ą70 > ķ>V z÷Mł
>PoŽ¬l $Ų² Ų²@Ų²šĪ°RgŚēɾ ¼{~) š ’§ŹIhķR^ dńĮŪ¾9° ĶwVs5Į <ą> 7 G`NÆeŖĆ °Apøąe0Č ½ś
t ĄMąG'īiŹü× ņpöG’ %ŗ
šš¶Ķ Pt ČŅ,ą`ĮjŠaP0 f0&w0°×yņ± ņ±@ņ±`ņÆŠmPß®²X® dAś :y’ŪėĆN{+jģ? M éoŠ 6°ÕpPPQĄ]@÷ C 7Øo v#` 0ĪgĄūn @' °×rĄ»q Ts å+pśĒ~(Z This chapter provides information about this release of the Oracle Database Gateway for APPC. It contains the following section: The following product components are included in the product installation media: Oracle Database Gateway for APPC, release 11.2 Oracle Net, release 11.2 The following sections describe the changes and enhancements unique to the 11g release of the gateway: The Gateway Password Encryption tool ( There is full IPv6 support between Oracle databases and the gateway but IPv6 is not yet supported between the gateway and IMS Connect. 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 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 Floating Point Data Type Conversion Is Not Supported Conversion of the floating point datatype 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 " This appendix describes the gateway initialization file location and lists the gateway initialization parameters supported by the Oracle Database Gateway for APPC specifically for the SNA protocol. These parameters are fully documented in Section 11.1, "Migrating an Existing Gateway Instance to New Release Using SNA Protocol". In addition, this appendix contains sample listener.ora and tnsnames files for a gateway using SNA. This appendix contains the following section: The parameter file for the gateway is located in the Note: The PGA parameters control the APPC interface portion of the gateway. PGA parameters are specified using the where: Table A-1 provides a list of PGA parameters and their descriptions. Table A-1 PGA Parameters for Gateway Using SNA where: PGA transaction capability. This controls whether updates are allowed through the gateway. The following are valid values: The default is Incoming The default is The Oracle Net service name for the Oracle database in which the gateway maintains its transaction log. This parameter can be fromĀ There is no default value. The Oracle password to be used by the gateway when connecting to the Oracle database specified by the There is no default value. The Oracle userĀ ID to be used by the gateway when connecting to the Oracle database specified by the There is no default value. The password to be used by the gateway when allocating an APPC conversation with the transaction specified by the There is no default value. The TP name of the transaction installed in the online transaction processor (OLTP) for commit-confirm The default value is The userĀ ID to be used by the gateway when allocating an APPC conversation with the transaction specified by the There is no default value. 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: The default is For further information about these options, refer to Chapter 10, "Security Requirements". PGA trace level. This controls tracing output written to The default isĀ Any value between When choosing a setting for the The In cases where the RTPs perform updates to foreign databases, there are two options for Each of these options provides protection against data integrity problems by permitting If the OLTP has LU6.2 Each of the Because the distributed transaction capability of the Oracle database is affected by the 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 When it is necessary to update resources on both the Oracle side and the OLTP side, a All that is necessary to set up multiple gateway instances is to set up the following for each instance: an entry in the an entry in the a database link in the Oracle database that specifies the alias defined in the Note that the gateway instances can share one common directory structure and use the same executables. For example, to set up two gateways, Define two aliases in Define two database links in the Oracle database , one connecting to Finally, create the initialization files In The same steps can be used to set up additional gateway instances. When deciding upon the setting for the One special case for the use of This chapter outlines the steps needed to configure the Oracle database for a gateway using the SNA protocol on the Microsoft Windows platform. It also shows you how to configure commit-confirm, should you choose to implement it. This chapter also provides the steps necessary to verify installation and configuration of the gateway components, including optional commit-confirm. It contains the following sections: Integrating Server Configuration: First-Time Gateway Installations Upgrading or Migrating the Oracle Database from Previous Gateways Configuring the Oracle Database Gateway for APPC using SNA involves working with the following components: the Oracle database your Microsoft Windows system your network the OLTP This chapter requires you to input parameters unique to your system in order to properly configure the gateway and SNA communications interface. Refer to Appendix D, "Configuration Worksheet" for a worksheet listing the installation parameters 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. There are three ways to establish the gateway-Oracle database relationship when you are installing or upgrading/migrating the gateway: When the Oracle Database and the gateway are installed in the same ORACLE_HOME on the same machine When the Oracle Database and the gateway are installed on separate machine When the Oracle Database and the gateway are on the same machine but in different directories Depending on the location of your gateway and your Oracle database , you may need to transfer some of the gateway administrative files to the location where your Oracle database is installed. Follow the instructions suitable to your combination of the gateway-Oracle database locations listed below. When the Oracle Database and the gateway are installed in the same ORACLE_HOME on the same machine You do not need to transfer files. Proceed to "Integrating Server Configuration: First-Time Gateway Installations". When the Oracle Database and the gateway are installed on separate machine Locate the gateway administrative files in the gateway Now, locate the gateway demo files and subdirectories in the gateway's 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 gateway Note: Refer to the Oracle Database Gateway for APPC User's Guide for information about generating TIPs using PGAU. When the Oracle Database and the gateway are on the same machine but in different directories You must change your gateway's Oracle home to the Oracle database 's Oracle home directory. For example, if your gateway's Oracle home is set as follows: and your server's Oracle home is located in the Now create the directories with the following commands: Use whatever file transfer mechanism is available on your system to copy all the You may also transfer the demo files from the gateway directory to the Oracle database directory. Copy the files and the directory recursively from the gateway Oracle home For example: Note: Refer to the Oracle Database Gateway for APPC User's Guide for information about generating TIPs using PGAU. If this is a first-time installation, then proceed with "Integrating Server Configuration: First-Time Gateway Installations". If this is an upgrade, then proceed with "Upgrading or Migrating the Oracle Database from Previous Gateways". Following those steps, you may want to perform the Optional Configuration Steps to Permit Multiple Users,. Follow these steps to configure your Oracle database if you have installed Oracle Database Gateway for APPC for the first time: Ensure that the From SQL*Plus, enter the following command: The If the From SQL*Plus, run the utlraw.sql and prvtrawb.plb scripts in the Oracle database 's Ensure that the If necessary, then use SQL*Plus to connect to the Oracle database as user From SQL*Plus, enter the following command: The If you do not see this output, then you must create the If the Install the Install the Heterogeneous Services (HS) catalogs. If necessary, use SQL*Plus to connect to the Oracle database as user Enter the following command: The If it is necessary to create the Heterogeneous Services catalog, then enter the following command: Create a public database link to access Oracle Database Gateway for APPC: Use SQL*Plus to connect to the Oracle database as user Create the gateway administrator user Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the pgacr8au.sql script in the The initial password defined for Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the From SQL*Plus, connect to the Oracle database as user Grant execution privileges on Install the TIP trace access PL/SQL routines. These routines require that the If necessary, then use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the Install the Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the From SQL*Plus, run the 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 user Install the Install the The If the If you do reinstall the package specifications, then 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: TIPs were split into separate specification and body files in releaseĀ 3.3 to avoid cascaded recompilations in later releases. From SQL*Plus, run the If necessary, then use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the After the scripts have run, repeat Steps 1b and c in Section 8.4, "Upgrading or Migrating the Oracle Database from Previous Gateways". Then, proceed to the section titled "Upgrading PGAU from Previous Gateway Releases". Note: You may 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 (PG DD), a versionĀ 9 gateway cannot communicate with a versionĀ 10 data dictionary. So, if you upgrade your data dictionary to versionĀ 10, no gateways which were configured with a versionĀ 9 data dictionary will be able to communicate with it. The following configuration steps are optional. Perform these steps if you want to permit users other than Create public synonyms for the PG DD to allow other users to access the tables: Create roles for accessing the PG DD, performing definitions of transactions, and generating TIP specifications. The Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the Grant access to PGA required packages. TIP developers require access to the following PL/SQL packages, which are shipped with the Oracle database : Explicit grants to execute these packages must be made to TIP developers. These grants can be private, as in the following example: Alternatively, these grants can be public, as in the following example: You can use either private or public grants. Both grants 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 Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the suitable script ( If you are using private grants, then repeat this step for each userĀ ID requiring access to the packages. or 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 Call PGAU in the directory path where the PGAU control files are generated and where TIPs are stored: For more information about the Note that it is not necessary to define the PG DD entries again. Call SQL*Plus in the same directory path where the newly-generated TIP specifications are stored. For more information about the 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, Note: The The parameters fall into two categories: gateway initialization parameters These parameters control the general operation of the gateway in the Oracle environment. Important: PGA parameters control the APPC interface portion of the gateway. Use the If you do not plan to configure commit-confirm, then proceed to"Verifying the Gateway Installation and OLTP Configuration". Note: 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, and configuring the OLTP. All these steps must be performed before attempting to use any application that uses commit-confirm. The Oracle database 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 Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the From SQL*Plus, run the Disconnect from the Oracle database . The gateway initialization parameters are described in Appendix A, "Gateway Initialization Parameters for SNA Protocol". The parameters necessary for commit-confirm support in the gateway are: These parameters should be added to your Refer to Appendix A, "Gateway Initialization Parameters for SNA Protocol" for full information about the gateway initialization parameters supported by the Oracle Database Gateway for APPC. Configuration of the OLTP includes the following: defining and installing the commit-confirm transaction log database defining and installing the commit-confirm forget/recovery transaction defining and installing the sample commit-confirm applications provided with the gateway. Note: Detailed instructions for configuring the Transaction Server for z/OS and IMS/TM are provided in the Refer to Chapter 5, "Implementing Commit-Confirm (SNA Only)" in the Oracle Database Gateway for APPC User's Guide for detailed information about commit-confirm. You will take steps to verify configuration of commit-confirm later in this chapter, in Section 8.9.3, "Verifying OLTP Configuration for Commit-Confirm". However, first proceed to Section 8.9 to verify the gateway installation. 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, then follow the steps to verify the OLTP configuration for commit-confirm. Note: To verify the gateway software installation using the database link PGA previously created, perform the following steps: Using SQL*Plus, connect to the Oracle database as user Run The server version number banner appears at your terminal. You will receive the following output: Run You will receive the following output: The procedure for verifying the OLTP configuration varies, depending on which OLTP you are using and depending on the 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 for verifying the installation. Attention: If your OLTP is CICS Transaction Server for z/OS, then perform the following steps to verify the CICS configuration. To verify that the The following output appears at your terminal: From the Windows platform, modify the pgacics.sql file which resides at 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: Log on to the CICS Transaction Server for z/OS and enter this transaction, where This transaction activates the CICS connection to Windows. Use SQL*Plus to connect to the Oracle database as The following message appears: The CICS Transaction Server for z/OS installation verification is complete. If the OLTP is IMS/TM, then perform the following steps to verify the IMS/TM configuration: To verify that the The following output appears on the terminal: From a Windows platform, modify the the IMS/TM transaction ID the side profile name the logmode entry name The following message appears: The IMS/TM installation verification is now complete. If the OLTP is APPC/MVS, then perform the following steps to verify the APPC/MVS configuration: Verify that the APPC/MVS subsystem is active. From the Windows platform, modify the the APPC/MVS transaction ID the side profile name the logmode entry name Run The following message appears: The APPC/MVS installation verification is now complete. If you chose to configure commit-confirm in Section 8.8, "Configuring Commit-Confirm", then the following section will assist you in verifying the configuration. Note: 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: 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 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 Installing forget/recovery transactions in the OLTP. These are provided in the Using the sample commit-confirm transaction log databases and subroutines. For Transaction Server for z/OS, a sample DB2 update transaction, 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 the OLTP. The Oracle Database Gateway for APPC package contains sample PL/SQL procedures and OLTP transaction programs that demonstrate the capabilities of the gateway. Samples are provided for the following: APPC/MVS z/OS dataset information CICS Transaction Server for z/OS DB2 inquiry DB2 multirow 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 update (CPI-C) Additional samples are added to the distribution media in later releases of the product. Wherever possible, the 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 Figure 1-1 provides an illustration of the relationship between the gateway and the Oracle database on a Windows 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. The figure is an illustration of the relationship between SNA Server definitions and the Host VTAM definitions. The surrounding text adequately describes the concepts. End of description. 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. Migrating to new instances of the 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 will 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 the Oracle Database Gateway for APPC for Microsoft Windows. It contains the following sections: 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's 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". Install the new release of the gateway in a separate directory as outlined in Chapter 4, "Installing the Gateway". Caution: Copy the Note that if you are migrating from Release 9.0.1 or earlier of the gateway, then 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 will help ensure minimal downtime between changes to different gateway instances. The 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 This release of the Oracle Database Gateway for APPC introduces new and changed initialization parameters if you are migrating from version 4 gateway to release 11.2 of the gateway. Note: If you are using the gateway's TCP/IP support for IMS Connect, then you will not be migrating from versionĀ 4 to the current release of the gateway. However, you will need to place valid Heterogeneous Services parameters into your This chapter contains references to the particular HS parameters you need to run the gateway. Note: New Gateway Initialization Parameters The following parameters are in the gateway initialization file ( Note: Renamed Gateway Initialization File Parameters Following is a list of the gateway initialization file (initsid.ora) parameters that have been renamed in this release of the gateway, the parameters' former names are shown in parentheses. Obsolete Parameters The following parameters are now obsolete. Please remove them from your configuration files: The following startup shell script parameter must be added to initsid.ora if you are migrating from versionĀ 4 or versionĀ 8 gateway to the current release of the Oracle Database Gateway for APPC: The following sections are for users who have an existing release of the gateway using the SNA protocol but who wish to switch to using TCP/IP support for IMS Connect. The TCP/IP support for IMS Connect feature in this release of the gateway allows you to continue to use existing TIPs. Follow these instructions: Make sure you have used the Refer to Chapter 9, "Gateway Configuration Using TCP/IP Communication Protocol" for instructions on loading the Make sure that the Use PGAU to regenerate the IMS TIPs. Add the following new TCP/IP parameters to the initsid.ora file: You will find descriptions and information about adding these parameters in Section 11.1.5, "Parameter Changes: Version 4 to Release 11.2 of the Gateway". You will also find descriptions of the parameters in Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol". Note: If you have existing TIPs that were generated previously on a gateway using the SNA protocol and you want to use the new TCP/IP feature, then the TIPs will have to be regenerated by PGAU with mandatory This is due to the fact that the gateway assumes that the suitable user exit in IMS Connect is being used, which would translate between the suitable ASCII and EBCDIC character sets. Now that you have installed the gateway, this chapter will instruct you about how to configure the network. It contains the following section: The instructions in this section will show you how to configure the network whether your gateway is using 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.ora file: If you are using SNA: where: Or, if you are using TCP/IP: where: 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 In this example, If you are using the TCP/IP protocol adapter and if your gateway In this example, Make sure to start your defined listeners. Refer to the Oracle Database Net Services Administrator's Guide for more information about configuring the network. To see a sample listener.ora file refer to "Sample listener.ora File for a Gateway Using SNA" and "Sample tnsnames.ora File for a Gateway Using SNA" in Appendix A (if your communication protocol is SNA). To see a sample listener.ora file refer to"Sample listener.ora File for a Gateway Using TCP/IP" and "Sample tnsnames.ora File for a Gateway Using TCP/IP" in Appendix B (if your communication protocol is TCP/IP). Proceed with Configuring Your Communication Package for the Gateway If your communication protocol is SNA, you must now configure the SNA Server profiles for APPC connections. Proceed to Chapter 6, " Configuring the SNA Communication Package on Windows" If your communication protocol is TCP/IP, proceed to Chapter 7, "Configuring the OLTP". Copyright Ā© 1994-2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 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 is software or related documentation that 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065. This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. This software or hardware 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. If this document is in prerelease status: This documentation is in prerelease status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation. This appendix contains a list of terms and definitions pertaining to the gateway and its components and function. For a list of other terms and definitions associated with the gateway, refer to ChapterĀ 1 of the Oracle Database Gateway for APPC User's Guide. This appendix contains the following section: Following is a list of some of the terms and definitions used in this edition of the Oracle Database Gateway for APPC Installation and Configuration Guide. This file is known as The Oracle Database Gateway for APPC provides prebuilt remote procedures. In general, the following three remote procedures are used: Refer to "Remote Procedural Call Functions" in this guide and to Appendix B, "Gateway RPC Interface" in the Oracle Database Gateway for APPC User's Guide for more information about gateway remote procedures. 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 Procedural Gateway Administration (PGA) is a general reference within this guide to all or most components comprising the Oracle Database Gateway for APPC. This term is used when references to a specific product or component are too narrow. Procedural Gateway Definition Language (PGDL) is the collection of statements used to define transactions and data to the PGAU. PL/SQL Stored Procedure Specification (PL/SQL package) 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 "UTL_RAW Functions" in 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 D of the Oracle Database Gateway for APPC User's Guide for supported numeric datatype conversions. This chapter outlines the steps needed to configure the Oracle database for a gateway using TCP/IP for IMS Connect on your Microsoft Windows platform. It also provides the steps necessary to verify installation and configuration of the gateway and OLTP components. It contains the following sections: Configuring the Oracle Database Gateway for APPC using TCP/IP support for IMS Connect involves working with the following components: the Oracle database your Windows system your network the OLTP This chapter requires you to input parameters unique to your system in order to properly configure the gateway and TCP/IP communications interface. Refer to Appendix D, "Configuration Worksheet" for a worksheet listing the installation parameters 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. There are three ways to establish the gateway-Oracle database relationship when you are installing or upgrading/migrating the gateway: When the Oracle Database and the gateway are installed in the same ORACLE_HOME on the same machine; When the Oracle Database and the gateway are installed on separate machine; or When the Oracle Database and the gateway are on the same machine but in different directories Depending on the location of your gateway and your Oracle database , you may need to transfer some of the gateway administrative files to the location where the Oracle database is installed. Follow the instructions suitable to your combination of the gateway-Oracle database locations listed below. When the Oracle Database and the gateway are installed in the same ORACLE_HOME on the same machine You do not need to transfer files. Proceed to "Configuring the Oracle Database : First Time Installation". When the Oracle Database and the gateway are installed on separate machine Locate the gateway administrative files in the gateway Now locate the gateway demo files and subdirectories in the gateway Copy the Optional Steps: If you want to run When the Oracle Database and the gateway are on the same machine but in different directories You must change your gateway's Oracle home to the Oracle database 's Oracle home directory. For example, if your gateway's Oracle home is set as follows: and your server's Oracle home is located in the ' Now, create the directories with the following commands: Use whatever file transfer mechanism is available on your system to copy all the You may also transfer the demo files from the gateway directory to the Oracle database directory. Copy the pgavsn.sql and You may also copy the Optional Steps: If you want to run Proceed to "Configuring the Oracle Database : First Time Installation". Following those steps, you may want to perform the Optional Configuration Steps to Permit Multiple Users,. Follow these steps to configure the Oracle database after installing the Oracle Database Gateway for APPC. Ensure that the From SQL*Plus, enter the following command: The If the Use SQL*Plus to connect to the Oracle database as From SQL*Plus, run the utlraw.sql and Ensure that the If necessary, then use SQL*Plus to connect to the Oracle database as user Enter the following command: The If you do not see this output, then you must create the If the Install the Install the Heterogeneous Services (HS) catalogs. If necessary, then use SQL*Plus to connect to the Oracle database as user Enter the following command: The If the If it is necessary to create the Heterogeneous Services catalog, then enter the following command: Create a public database link to access the Oracle Database Gateway for APPC: Use SQL*Plus to connect to the Oracle database as user Create the gateway administrator user Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the The initial password defined for Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the From SQL*Plus, connect to the Oracle database as user Grant execution privileges on Ensure that the Refer to "Output for the pg4tcpmap Tool" in Appendix B for a sample of the output from the Use SQL*Plus to connect to the Oracle database as user Enter the following command: Both Following is the result of the second select statement: If the select statements produce the preceeding output on the screen, then you can skip Step C. 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 c. From SQL*Plus, run the Install the TIP trace access PL/SQL routines. These routines require that the If necessary, then use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the Install the Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the From SQL*Plus, run the Note: If you have existing TIPs that were generated previously on a gateway using the SNA protocol and you want to use the new TCP/IP feature, then the TIPs will have to be regenerated by PGAU with mandatory This is due to the fact that the gateway assumes that the appropriate user exit in IMS Connect is being used, which would translate between the suitable ASCII and EBCDIC character sets. 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 user Install the Install the The If the If you do reinstall the package specifications, then 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. Note: 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: If necessary, then use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the Step 2: Repeat installation of After the scripts have run, repeat Steps 1a and 1b in Section 9.4, "Upgrading or Migrating the Oracle Database from Previous Gateways" and then, proceed to Section 9.4.2, "Upgrading PGAU from Previous Gateway Releases". Note: Upgrade the PG DD as follows before execution the new PGAU: If necessary, then use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the The following configuration steps are optional. Perform these steps if you want to allow users other than Create public synonyms for the PG DD to allow other users to access the tables: Create roles for accessing the PG DD, performing definitions of transactions, and generating TIP specifications. The Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the Grant access to PGA required packages. TIP developers require access to the following PL/SQL packages, which are shipped with the Oracle database : Explicit grants to execute these packages must be made to TIP developers. These grants can be private, as in the following example: Alternatively, these grants can be public, as in the following example: 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 Use SQL*Plus to connect to the Oracle database as user From SQL*Plus, run the suitable script ( or 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 Call PGAU in the directory path where the PGAU control files are generated and where TIPs are stored: For more information about the Note that it is not necessary to define the PG DD entries again. Call SQL*Plus in the same directory path where the newly-generated TIP specifications are stored. PGAU For more information about the 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, Section 9.7, "Configuring the Gateway". To configure the gateway, follow the instructions given subsequently: Tailor the gateway parameters. There are a number of parameters specific to the Oracle Database Gateway for APPC when it is using TCP/IP for IMS Connect. These are supplied in the gateway parameter file, Note: The initsid.ora file contains both APPC and TCP/IP parameters, separated by a description. You must modify the The parameters fall into two categories: gateway initialization parameters These parameters control the general operation of the gateway in the Oracle environment. Important: PGA parameters control the TCP/IP interface portion of the gateway. Use the Gateway users who wish to employ the TCP/IP protocol do so by using the The In PGAINIT TIP, for example, the user must specify a side profile name. The SNA protocol recognizes and uses the parameter. In this release of the gateway, the Before executing Chapter 6 of the Oracle Database Gateway for APPC User's Guide contains a list of To operate this tool, execute the following command: Refer to "Output for the pg4tcpmap Tool" for a sample of the To verify the gateway installation and the OLTP configuration, perform the following procedures after installing the gateway. Note: 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 user Run The server version number banner appears at your terminal. You will receive the following output: Run You will receive the following output: Use the following procedure to verify the OLTP configuration. Attention: 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. To verify that the The following output appears on your terminal: Attention: From your Windows platform, modify the the IMS/TM transaction ID the side profile name the 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 The following message appears: Your IMS/TM installation verification is now complete. The following are optional steps that you can perform as necessary. Installation of the sample applications for the OLTP is recommended to help you to fully understand how the gateway works and how it interfaces with the OLTP. 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: For more information, refer to the Samples are provided for IMS/TM: IMS inquiry using Additional samples are added to the distribution media in later releases of the product. Wherever possible, the 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
PK»5«E> 9 PK 5&A
OEBPS/apa.htmÉe6
2 Release Information
2.1 Product Set
2.2 Changes and Enhancements
2.2.1 Gateway Password Encryption Tool
g4drpwd) 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 Microsoft Windows for details.
2.2.2 Partial IPv6 Support
2.3 Known Restrictions
2.3.1 Known Restrictions for the Gateway
PIC G datatypes since versionĀ 3.4. However, the non-numeric character data (such as $, (,), +, -,.) that is allowed in DISPLAY datatypes and PICĀ 9 edit masks must still be specified in EBCDIC. The non-numeric character data is not subject to MBCS translation.PIP data in this release of the Oracle Database Gateway for APPC.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.
PKžREĪe Ée PK 5&A
OEBPS/ch9.htm ’
A Gateway Initialization Parameters for SNA Protocol
A.1 Gateway Initialization Parameter File Using SNA Protocol
%ORACLE_HOME%\dg4appc\admin directory and is called initsid.ora.
initsid.ora file contains both SNA and TCP/IP parameters. You must modify these files with the suitable parameters.
A.1.1 PGA Parameters
SET gateway initialization parameter. For example:
SET pga_parm=value
pga_parm is one of the PGA parameter names in the list that follows; andvalue is a character string with contents that depend on pga_parm
Parameter Description
logpath specifies the destination at which STDERR is reopened. LOG_DESTINATION specifies a directory only and STDERR is reopened to logpath\sid_pid.logsid is the sid namepid is the process ID assigned to the gateway
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.SINGLE_SITE.
APPC CONFIRM request handling option. This controls what the gateway does when an APPC CONFIRM request is received from the remote transaction program (RTP). This parameter has meaning only when the conversation is running with SYNCLEVEL > 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.REJECT.
1 to 255Ā characters long. This parameter is required only when PGA_CAPABILITY parameter is set to COMMIT_CONFIRM.
PGA_LOG_DB parameter. The password can be fromĀ 1 to 30Ā characters long. This parameter is required only when PGA_CAPABILITY parameter is set to COMMIT_CONFIRM. The password can be encrypted. For more information about encrypting the password, refer to Section 10.6, "Passwords in the Gateway Initialization File".
PGA_LOG_DB parameter. The userĀ ID can be fromĀ 1 to 30Ā characters long. This parameter is required only when PGA_CAPABILITY parameter is set to COMMIT_CONFIRM.
PGA_RECOVERY_TPNAME parameter. The password can be fromĀ 1 to 8Ā characters long. This parameter is required only when PGA_CAPABILITY parameter is set to COMMIT_CONFIRM and PGA_SECURITY_TYPE parameter is set to PROGRAM. The password can be encrypted. For more information about encrypting the password, refer to Section 10.6, "Passwords in the Gateway Initialization File".
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 parameter is set to COMMIT_CONFIRM.RECO.
PGA_RECOVERY_TPNAME parameter. The userĀ ID can be fromĀ 1 to 8Ā characters long. This parameter is required only when PGA_CAPABILITY parameter is set to COMMIT_CONFIRM and PGA_SECURITY_TYPE parameter is set to PROGRAM or SAME.
NONE, which sends no security parametersSAME, which sends only a userĀ IDPROGRAM, which sends a userĀ ID and passwordNONE.
STDERR (the target of the LOG_DESTINATION parameter. The value must be an integer fromĀ 0 toĀ 255.0, indicating no tracing.1 and 255 will turn on tracing.
A.1.2 PGA_CAPABILITY Parameter Considerations
PGA_CAPABILITY parameter, take care to ensure that the correct setting is used based on what the RTPs will be doing.READ_ONLY setting should always be used when the RTPs are read-only, that is, when the RTPs perform no database updates. READ_ONLY should never be used when the RTPs perform database updates. For example, if the READ_ONLY setting is chosen, and if a RTP called by the gateway performs updates to a foreign database, then the Oracle database does not provide any integrity protection for those updates. Further, READ_ONLY mode allows a gateway transaction to be part of a distributed transaction that might update several other databases. If the gateway calls a RTP that performs updates in this situation and if a failure occurs, then the database updated by the RTP is out of sync with the other databases.PGA_CAPABILITY:SINGLE_SITECOMMIT_CONFIRMCOMMIT and ROLLBACK requests to be forwarded to the RTP and by informing the Oracle database about the distributed update and recovery capabilities of the gateway. The particular option chosen depends on the design of the RTPs and upon the capabilities of the OLTP where they execute.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 the Oracle database and the OLTP, with the restriction that only the OLTP can perform updates, and no updates can occur on the Oracle side.PGA_CAPABILITY options for update control imposes specific requirements on the RTP 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 8.8.3, "Configuring the OLTP for Commit-Confirm" in this guide. For SINGLE_SITE capability, the RTP is responsible for performing the suitable 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 command, the RTP must perform COMMIT processing and then respond to the gateway with an APPC CONFIRMED response. On receipt of a SEND_ERR command, the RTP must perform ROLLBACK processing.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.READ_ONLY gateway by an inquiry-only RTP, 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 RTPs which perform updates to foreign databases outside the scope of control of the Oracle database . Data can be read from any databases accessible to the Oracle database , and that data can be used to perform updates through the gateway.COMMIT_CONFIRM gateway can be used, provided that the OLTP and the RTPs are set up to implement COMMIT_CONFIRM.listener.ora file defining the sid of the gateway instancetnsnames.ora file defining an alias to be used to connect to the gateway instance defined in listener.oratnsnames.ora file in its USING parameter.PGAI and PGAU (for inquiry and update use, respectively), the following steps are required:tnsnames.ora that connect to the two new sids, PGAI and PGAU.PGAI and the other connecting to PGAU.initPGAI.ora and initPGAU.ora.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.
A.1.3 PGA_CONFIRM Parameter Considerations
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 suitable 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 issued a COMMIT request. In order 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.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/ROLLBACK to control updates on the IMS side of the conversation.
A.1.4 Sample listener.ora File for a Gateway Using SNA
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(COMMUNITY= TCP.world)
(Host = bay)
(PROTOCOL= TCP)
(Port= 2621)
)
(ADDRESS=
(COMMUNITY= TCP.world)
(Host = bay)
(PROTOCOL= TCP)
(Port= 2623)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PGA)
(ORACLE_HOME = C:\oracle\pga\11.2)
(PROGRAM = pg4asrv)
)
)
A.1.5 Sample tnsnames.ora File for a Gateway Using SNA
ORA920 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = bay.us.oracle.com)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ORA920.bay)
)
)
PGA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = bay)(PORT = 2621))
)
(CONNECT_DATA =
(SID = PGA)
)
(HS = OK)
)
PK y#Uų Kų PK 5&A OEBPS/img_text/g1_1trms.htmwü
8 Gateway Configuration Using SNA Communication Protocol
8.1 Before You Begin
8.2 Preparing to Configure a Gateway Installation/Upgrade
%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 's Oracle home directory.%ORACLE_HOME%\dg4appc\demo directory. Copy the pgavsn.sql and pgaecho.sql files into a similarly named directory in the Oracle database .%ORACLE_HOME%\dg4appc\demo\CICS files into a similarly named directory in the Oracle database .
%ORACLE_HOME%\dg4appc\demo directory, make sure that you have generated your required TIPs. You need to transfer the TIPs as well.
C:\> echo %ORACLE_HOME%
C:\oracle\pga\11.2
\oracle\pga\11.2 directory, then you need to do the following:
C:\> SET ORACLE_HOME=C:\oracle\pga\11.2
C:\> cd %ORACLE_HOME%
C:\> mkdir dg4appc
C:\> mkdir dg4appc\admin
.sql, .pkh, and .pkb files from the gateway Oracle home %ORACLE_HOME%\dg4appc\admin directory to the Oracle database 's Oracle home %ORACLE_HOME%\dg4appc\admin directory.%ORACLE_HOME%\dg4appc\demo directory to the Oracle database %ORACLE_HOME%\dg4appc\demo directory.
C:\> cd %ORACLE_HOME%\dg4appc
C:\> mkdir\demo
C:\> cd demo
C:\> xcopy C:\oracle\pga\11.2\demo /E /I /Q
%ORACLE_HOME%\dg4appc\demo directory, make sure that you have generated the required TIPs. You need to transfer the TIPs as well.
8.3 Integrating Server Configuration: First-Time Gateway Installations
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.
SQL> DESCRIBE UTL_RAW
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.DESCRIBE statement indicates success, then your Oracle database has UTL_RAW installed and you can proceed to StepĀ 2.%ORACLE_HOME%\rdbms\admin directory, in the following order:
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @utlraw.sql
SQL> @prvtrawb.plb
DBMS_OUTPUT standard PL/SQL package is enabled on your Oracle database . The sample programs and installation verification programs on the distribution media use this standard package.SYS.
SQL> DESCRIBE DBMS_OUTPUT
DESCRIBE statement produces output on your screen. If you browse through that output, you should see some functions, including a put_line function.DBMS_OUTPUT package. Refer to the Oracle Database Advanced Application Developer's Guide for more information about creating the DBMS_OUTPUT package. After successful installation of the DBMS_OUTPUT package, issue the DESCRIBE statement.DESCRIBE statement indicates success, then your Oracle database has DBMS_OUTPUT created, and you can proceed to StepĀ 3.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.SYS.
SQL> DESCRIBE HS_FDS_CLASS
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. The next step will create the Heterogeneous Services catalog.
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @caths.sql
SYSTEM. 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'
PGAADMIN and install the PG DD.SYSTEM.%ORACLE_HOME%\dg4appc\admin directory. This script creates the PGAADMIN userĀ ID.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgacr8au.sql
PGAADMIN.pgddcr8.sql script in the %ORACLE_HOME%\dg4appc\admin directory. This script installs the PGĀ DD.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddcr8.sql
SYS.DBMS_PIPE to PGAADMIN:
SQL> GRANT EXECUTE ON DBMS_PIPE TO PGAADMIN
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 Advanced Application Developer's Guide.PGAADMIN.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgatiptr.sql
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").PGAADMIN.gpglocal.pkh script in the %ORACLE_HOME%\dg4appc\admin directory. This script compiles the GPGLOCAL package specification.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @gpglocal.pkh
gpglocal.pkb script in the %ORACLE_HOME%\dg4appc\admin directory. This script compiles the GPGLOCAL package body.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @gpglocal.pkb
8.4 Upgrading or Migrating the Oracle Database from Previous Gateways
SYS.UTL_RAW package body. From SQL*Plus, run the prvtrawb.plb script from the %ORACLE_HOME%\rdbms\admin directory. This script upgrades the UTL_RAW package body.
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @prvtrawb.plb
UTL_PG package body. From SQL*Plus, run the prvtpgb.plb script from the %ORACLE_HOME%\rdbms\admin directory. This script upgrades the UTL_PG package body.
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @prvtpgb.plb
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 Section 8.4.1, "If You Must Reinstall Package Specifications".
8.4.1 If You Must Reinstall Package Specifications
UTL_RAW or UTL_PG package has been invalidated or removed, then the prvtrawb.plb and prvtpgb.plb scripts may not complete successfully, then, you might have to reinstall the package specifications.
%ORACLE_HOME%\dg4appc\admin directory.utlraw.sql script:SYS.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:
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @utlraw.sql
SQL> @utlpg.sql
8.5 Configuring the Oracle Database for Gateways to Coexist
8.6 Optional Configuration Steps to Permit Multiple Users
PGAADMIN to perform PG DD operations using PGAU.PGAADMIN user can grant these roles to other users as necessary.PGAADMIN.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddcr8r.sql
C:\> 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
C:\> 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
%ORACLE_HOME%\dg4appc\admin directory. The pgddapub.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's userĀ ID:PGAADMIN.pgddapub.sql or pgddadev.sql) from the %ORACLE_HOME%\dg4appc\admin directory. The script performs the necessary grants as dKx“escribed earlier. You are prompted for the required userĀ IDs, passwords, and database specification strings.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddapub.sql
SQL> @pgddadev.sql
GENERATE statement.
C:\> pgau
PGAU> CONNECT PGAADMIN\pgaadmin@database_specification_string
PGAU> GENERATE tranname
PGAU> EXIT
GENERATE command, refer to the PGAU GENERATE command section in Chapter 2 of the Oracle Database Gateway for APPC User's Guide.
C:\> sqlplus tip_owner\pw@database_specification_string
SQL> @tipname.pkh
SQL> @tipname.pkb
SQL> exit
PGAU GENERATE produces the TIP in two output file, a specification and a body. You must compile both, first the specification and then the body.GENERATE command, refer to the PGAU GENERATE command section in Chapter 2 of the Oracle Database Gateway for APPC User's Guide.
8.7 Configuring the Gateway
initsid.ora, which is in the %ORACLE_HOME%\dg4appc\admin directory. A sample gateway parameter file, initPGA.ora, is provided in this subdirectory.
initsid.ora file, substitute your dg4appc SID name for "sid " in this file name.
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.
PGA_CAPABILITY parameter.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.
8.8 Configuring Commit-Confirm
8.8.1 Configuring the Oracle Database for Commit-Confirm
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.SYSTEM.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, then you can use the ALTER USER command to change the password. For further information, refer to the Oracle Database SQL Language Reference.PGADBA.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.pgacclog.sql script from the %ORACLE_HOME%\dg4appc\admin directory. This script creates the PGA_CC_LOG PL/SQL stored procedure used by the gateway server for updating the PGA_CC_PENDING table.
8.8.2 Configuring Gateway Initialization Parameters for Commit-Confirm
PGA_CAPABILITYPGA_LOG_DBPGA_LOG_USERPGA_LOG_PASSPGA_RECOVERY_USERPGA_RECOVERY_PASSPGA_RECOVERY_TPNAMEinitsid.ora file, where sid is the gateway SID for the commit-confirm gateway.
8.8.3 Configuring the OLTP for Commit-Confirm
%ORACLE_HOME%\dg4appc\demo\CICS\README.doc and %ORACLE_HOME%\dg4appc\demo\IMS\README.doc files, respectively.
8.9 Verifying the Gateway Installation and OLTP Configuration
8.9.1 Verifying the Gateway Installation
PGAADMIN.%ORACLE_HOME%\dg4appc\demo\pgavsn.sql.
C:\> cd %ORACLE_HOME%\dg4appc\demo
SQL> @pgavsn.sql
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.
%ORACLE_HOME%\dg4appc\demo\pgaecho.sql.
C:\> cd %ORACLE_HOME%\dg4appc\demo
SQL> @pgaecho.sql
==> Congratulations, your installation was successful. <==
8.9.2 Verifying the OLTP Configuration
8.9.2.1 CICS Verification
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 configured your CICS Transaction Server for z/OS for the gateway:
FLIP THIS MESSAGE
EGASSEM SIHT PILF
%ORACLE_HOME%\dg4appc\demo\CICS\pgacics.sql.name is the name of the CONNECTION definition installed by the DFHCSDUP job you ran in the CICS configuration steps:
CEMT SET CONNECTION(name) ACQUIRED
PGAADMIN.
C:\> cd %ORACLE_HOME%\dg4appc\demo\CICS
SQL> @pgacics.sql
==> Congratulations, your gateway is communicating with CICS <==
8.9.2.2 IMS/TM Verification
FLIP transaction is installed correctly, log on to the IMS/TM system and enter the following transaction, replacing FLIP with the transaction ID you chose for FLIP when you configured the IMS/TM system for the gateway:
FLIP THIS MESSAGE
EGASSEM SIHT PILF
pgaims.sql file, which resides 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:
C:\> cd %ORACLE_HOME%\dg4appc\demo\IMS
SQL> @pgaims.sql
==> Congratulations, your gateway is communicating with IMS/TM <==
8.9.2.3 APPC/MVS Verification
pgamvs.sql file, which resides 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:pgamvs.sql.
C:\> cd %ORACLE_HOME%\dg4appc\demo\MVS
SQL> @pgamvs.sql
=> Congratulations, your gateway is communicating with APPC/MVS <=
8.9.3 Verifying OLTP Configuration for Commit-Confirm
%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:pgacclg.asm files. They can be used in the applications to reduce the complexity of the code changes to the programs.CALL statement or its equivalent in the application's programming language. Both these subroutines are written in 370 assembler to eliminate any interlanguage interface complexities and compiler dependencies.pgareco.asm files. Forget/recovery transactions must be accessible through APPC so that the gateway can call them to forget a transaction once it has been successfully committed, and to query a transaction's 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.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.
8.10 Performing Postinstallation Procedures
8.10.1 Installing Sample Applications
README.doc files in the following directories:%ORACLE_HOME%\dg4appc\CICS\sample_CICS_applications.txt%ORACLE_HOME%\dg4appc\IMS\sample_IMS_applications.txt%ORACLE_HOME%\dg4appc\MVS\sample_MVS_applications.txt
PKĶ¦[“łB ōB PK 5&A
OEBPS/toc.ncxÖ)ļ
11 Migration from Existing Gateways
11.1 Migrating an Existing Gateway Instance to New Release Using SNA Protocol
11.1.1 StepĀ 1:Ā Install the New Release
11.1.2 StepĀ 2:Ā Transfer initsid.ora Gateway Initialization File Parameters
initsid.ora file from the old gateway instance to the new instance.PGA_TRACE is not supported, you will need to modify the parameter to TRACE_LEVEL, instead.
11.1.3 Backout Considerations When Migrating to New Releases
11.1.4 Oracle Net Considerations
tnsnames.ora file. Add an (HS=) clause to communicate to Oracle Net that the gateway uses HS facilities. For more information, refer to "Configuring the Oracle Network for the Gateway".
11.1.5 Parameter Changes: Version 4 to Release 11.2 of the Gateway
initsid.ora file.
initsid.ora):
HS_ parameters are specific to Oracle Heterogeneous Services. For details on HS parameters, refer to the Oracle Database Administrator's Guide.MODESERVER_PATHERROR_LOGGINGERROR_REPORTINGERRORTAGGATEWAY_SIDGROUP_BY_OFFGTWDEBUGINCREMENT_CURSORSINIT_CURSORSLISTMAX_LOG_SIZEOPTIMIZE_FILE_OPENORDER_BY_OFFRESOLVE_BINDSRETRYSETSNMP_SUPPORTSQL_TRACETRIM_CURSORSD_OPEN_CURSORSD_INIT_CURSORSD_INCREMENT_CURSORSD_TRIM_CURSORSPGA_TRACE
11.1.6 Parameter Changes: Version 8 or Earlier to Gateway Release 11.2
11.2 Migrating from an Existing Gateway Using SNA to TCP/IP
11.2.1 To Use Existing TIPs with Existing Side Profile Definitions
pg4tcpmap tool to insert valid parameter values into the PGA_TCP_IMSC table.PGA_TCP_IMSC table.LANGUAGE parameter in your TIPs is set to american_america_us7ascii.PGA_TCP_DBPGA_TCP_USERPGA_TCP_PASS
NLS_LANGUAGE and Side Profile Settings. Specify the suitable ASCII character set in the DEFINE TRANSACTION command.
PK”Į ¼ PK 5&A OEBPS/content.opfÅ :ą
5 Configuring Your Oracle Network
5.1 Configuring the Oracle Network for the Gateway
(SID_DESC=
(SID_NAME=PGA)
(ORACLE_HOME= C:\oracle\pga\11.2)
(PROGRAM=pg4asrv)
)
C:\oracle\pga\11.2 is your gateway Oracle home, and PGA is the gateway SID name.
(SID_DESC=
(SID_NAME=PGA)
(ORACLE_HOME= C:\oracle\pga\11.2)
(PROGRAM=pg4t4ic)
)
C:\oracle\pga\11.2 is your gateway Oracle home, and PGA is the gateway SID name.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:
pgaipc=
(DESCRIPTION =
(ADDRESS = (PROTOCOL = ipc) (KEY=key))
(CONNECT_DATA = (SID=PGA))
(HS=)
)
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.sid is PGA, then add the following entry to tnsnames.ora:
pgatcp=
(DESCRIPTION =
(ADDRESS = (PROTOCOL= TCP)(Host= gateway)(Port= port))
(CONNECT_DATA = (SID=PGA))
(HS=)
)
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.
PK]ü9tĪ É PK 5&A OEBPS/dcommon/prodbig.gif öłGIF87a ÷ ’’’!!!)))111BBBZZZsss„„„µµµĘĘĘĪĪĪÖÖÖŽŽŽēēēļļļ÷÷÷½µµ{{ZRRcZZ!!1!ŽÖĪ91)JB9B9)ĪĪĘÖÖĪēēŽkkc„„JJB991sscļ÷÷ÖŽŽŽēēµ½½½ĘĘZcc!! {„Öē„½ĘBZc!9B!c{ !)c{9Ę{„Z{{µcĪZ„ĘBĘ1µ)ʵĘs„½ Jk {µ{Z{µĪkĪBsZÖJĘ9µ1½)µZ{!Ę½{µ½ Bc½ŽsĪRĘsBc{½ 9Z Z½k„Īē½ÖkÖ Bk R½Öē„ĘŽ!BZ 9c )JJc{!))BZks{BcR{„JsBk9k)ZcµkĪ ! !B Zµ„1k!ZcµRBZµcĘ Z½JkBk1Z9c!R!cµ9kZR„ZµR B ZĘ9{ 9 9 !R 1{ 99R{ 1!1)c 1 J)1BÖŽ÷ ! B J Rļļ÷„„„kk{µ„„Ę½½ēµµŽŽkkēµµ÷RRs{{½ĪŽ{{½JJsssµŽBBkÖkkµ!!9ssĪ{{ēZZssēccĪJJZZ½RRµccŽRR½ZZÖ))cBB„JJĘ99„JJÖ!!c1199½11„99ĪZ11½!c!!))ĪZ!!ĘʵĘĪµ ! 1 B R c k { ½ „½µ÷)!cJBkZRZ , ’ HPą)X²ĘRõ ĆEåZÖ¬4jŪJ0 ¢@ "8pš YŅ“ESģYŗ3CĘ Ŗ@µ* U:lĪY0_ū0üė#
5tXš1E:ī Cć_ŗxŽżĀeK© T¢<¹ńOC(x rŌ' Jž©ēm1aĄś½0S%Č-IŅex D} 1ZŌi^są°E¦Ļß #
ų`¢qTv å©ÓFĖį¼Y»Ķ3č)PÖ¶e ĮOź@¬]ėåėģoąĮ
{(óbĄ½SÆ#|Æ·b“\±ŗ'YŠ$’ĄP tßŖæ¶Ī,Æ^ćXB.+ĪKW’o¹Ų³qc[ø=1
( #üH#ÆłGN8ćĢćN:UaE\čpÅ
(sĒ#ä„9c! mø 8b
DbI%zŻC9ē¼xEUA#Šč!9īxŁ.^8¤E i£LF² +¶($Dx¤X6É%@~ÉÅFÖ$:r)O=õ#g ±CcŽø¤O¦ēV Įēv,É xż£K2Ē4ß`hM±Å
6ōéw$¢Č ’ ŠŹ)§¼āĖ3E ¢¤ī &JČ x4BŖ·ŌĻ.ĘPćPd1Ltjć§ņH£ŪT3Ķ4ÖtSégBąšRģŃ'*u¢ HĀ^ųSĪ8ö¼Ī: 1Eįķ2I!īčŠćī ńĪė
÷B&d" &Ī;óČ#<ķüóĀ`qĘ_¤ tq¼ńI)¦¢Ī?^±ć;ķ°óŅ?°q |X62 ° 'éØó “0:ė- ?-²Ē6øį 4ōlšA Š't`×#0ą c{ąA @ P@ ;PK_£ć PK 5&A OEBPS/dcommon/doclib.gif
õžGIF89a ó 1’’’ļļ÷ÖŽēĘĪÖ½Ī½{kc{JsBc9Zs1Jk , @æČI«„vŹ Ų5a-”é5-vĘasEnq0&
óŅVF[|ÉOĀ ø @@°É48ŪŖpM(¬ 7*X(±ÅĘĪj¶o0Fq|uHu9(dK@ @Y ! mFt,„gN¬h¦%±
NµNø@±¶·¬
Ą§ F³¦ĖælŗN· duø_ĀŅg%½įā ;PKĻY@¹
PK 5&A OEBPS/dcommon/oracle-logo.jpgTj«’Ų’ą JFIF ’Ū C
$.' ",# (7),01444 '9=82<.342’Ū C
2! !22222222222222222222222222222222222222222222222222’Ą '7" ’Ä
’Ä µ } !1AQa"q2”#B±ĮRŃš$3br
%&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
¢£¤„¦§Ø©Ŗ²³“µ¶·ø¹ŗĀĆÄÅĘĒČÉŹŅÓŌÕÖ×ŲŁŚįāćäåęēčéźńņóōõö÷ųłś’Ä
’Ä µ w !1AQaq"2B”±Į #3RšbrŃ
$4į%ń&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
¢£¤„¦§Ø©Ŗ²³“µ¶·ø¹ŗĀĆÄÅĘĒČÉŹŅÓŌÕÖ×ŲŁŚāćäåęēčéźņóōõö÷ųłś’Ś ? ÷ś(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(¢
(Å QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE !KE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE QE zŠ³E7List of Figures
Oracle Legal Notices
Copyright Notice
Trademark Notice
License Restrictions Warranty/Consequential Damages Disclaimer
Warranty Disclaimer
Restricted Rights Notice
Hazardous Applications Notice
Third-Party Content, Products, and Services Disclaimer
Alpha and Beta Draft Documentation Notice
PKI>ĘR Z Z PK 5&A
OEBPS/apc.htm>Įę
Contents
List of Figures
List of Tables
Title and Copyright Information
Preface
1 Introduction to Oracle Database Gateway for APPC
2 Release Information
3 System Requirements
4 Installing the Gateway
5 Configuring Your Oracle Network
6 Configuring the SNA Communication Package on Windows
7 Configuring the OLTP
8 Gateway Configuration Using SNA Communication Protocol
9 Gateway Configuration Using TCP/IP Communication Protocol
10 Security Requirements
11 Migration from Existing Gateways
A Gateway Initialization Parameters for SNA Protocol
B Gateway Initialization Parameters for TCP/IP Communication Protocol
C Gateway Terminology
D Configuration Worksheet
Index
PKŠöÕC > PK 5&A
OEBPS/lot.htm®Qł
C Gateway Terminology
C.1 Gateway Term Definitions
initsid.ora and it contains parameters that govern the operation of the gateway. If you are using the SNA protocol, then refer to Appendix A, "Gateway Initialization Parameters for SNA Protocol" for more information. Refer to Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol" if your protocol is TCP/IP.PGAINIT, which initializes transactionsPGAXFER, which transfers dataPGATERM, which terminates transactionsdg4pwd 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.PGA_TCP_IMSC table.
PKzłEv³ ® PK 5&A OEBPS/ch10.htm ’
List of Tables
PKŻŚ½ŠŻŌ ÓŌ PK
5&Aoa«, mimetypePK 5&AĀµ&>
: iTunesMetadata.plistPK 5&AYuģē ā META-INF/container.xmlPK 5&Abž5ś; õ;
, OEBPS/ch8.htmPK 5&AbSß' Ś'
aB OEBPS/ch3.htmPK 5&AŖ„7R 2R {j OEBPS/ch11.htmPK 5&A[×ßpT O ī¼ OEBPS/cover.htmPK 5&Acjn½T O æ OEBPS/title.htmPK 5&AuÕ², ,
Ó OEBPS/ape.htmPK 5&AC >żīu éu
ż’ OEBPS/ch1.htmPK 5&A* ō«Éz Äz
&v OEBPS/ch4.htmPK 5&A5=%µ= 3
*ń OEBPS/ch6.htmPK 5&Af`X@< <
¢ OEBPS/apb.htmPK 5&AQ%ö+ ń+ ō» OEBPS/preface.htmPK 5&Aüü²ŗ )č OEBPS/index.htmPK 5&AŪW W u OEBPS/img/g1_1trms.gifPK 5&AU]Ž Ō ]Ķ OEBPS/img/g6_17vtam.gifPK 5&A"ņI¢ ] ] N OEBPS/img/g1_2arch.gifPK 5&A»5«E> 9
į« OEBPS/ch2.htmPK 5&AžREĪe Ée
ZÅ OEBPS/apa.htmPK 5&A y#Uų Kų
c+ OEBPS/ch9.htmPK 5&A½¶½ ó# OEBPS/img_text/g1_1trms.htmPK 5&AzįDFU P É' OEBPS/img_text/g6_17vtam.htmPK 5&ATgr m h* OEBPS/img_text/g1_2arch.htmPK 5&AĶ¦[“łB ōB #- OEBPS/ch12.htmPK 5&Aæķ',Ū Ö
Xp OEBPS/toc.ncxPK 5&A”Į ¼
n OEBPS/ch5.htmPK 5&A@5õŹ Å j¢ OEBPS/content.opfPK 5&A]ü9tĪ É
sĀ OEBPS/lof.htmPK 5&A_£ć |Č OEBPS/dcommon/prodbig.gifPK 5&AĻY@¹
ŃĪ OEBPS/dcommon/doclib.gifPK 5&A;mĆKYj Tj &Š OEBPS/dcommon/oracle-logo.jpgPK 5&Aüļü³¤ Ź: OEBPS/dcommon/contbig.gifPK 5&A µ@ OEBPS/dcommon/darbbook.cssPK 5&AMĪ¬Ü" ×" ! A OEBPS/dcommon/O_signature_clr.JPGPK 5&A³PzŲ -d OEBPS/dcommon/feedbck2.gifPK 5&Aė-“ÅĶ Č
e OEBPS/dcommon/feedback.gifPK 5&AĖ5 l OEBPS/dcommon/booklist.gifPK 5&AŗN ź6 1 żm OEBPS/dcommon/cpyr.htmPK 5&AŅ!:·3 . w OEBPS/dcommon/masterix.gifPK 5&AeÓŗ³1 , ņ OEBPS/dcommon/doccd.cssPK 5&Aæź7 į Ü h OEBPS/dcommon/larrow.gifPK 5&AśŖ„# OEBPS/dcommon/indxicon.gifPK 5&A×ĶS«' " ś OEBPS/dcommon/leftnav.gifPK 5&Ahu,Õ Š h OEBPS/dcommon/uarrow.gifPK 5&Al-ķO J OEBPS/dcommon/oracle.gifPK 5&A(ż ü OEBPS/dcommon/index.gifPK 5&AéöGCŁ Ō ^ OEBPS/dcommon/bookbig.gifPK 5&A£JV^Õ Š ~” OEBPS/dcommon/rarrow.gifPK 5&Ażę°p k £ OEBPS/dcommon/mix.gifPK 5&Ao"nR
M
L¦ OEBPS/dcommon/doccd_epub.jsPK 5&Av
I
ē° OEBPS/dcommon/toc.gifPK 5&Aé
r~$ 4² OEBPS/dcommon/topnav.gifPK 5&A1żF A ³ OEBPS/dcommon/prodicon.gifPK 5&A3(
#
,· OEBPS/dcommon/bp_layout.cssPK 5&A x[Ø? : Ä OEBPS/dcommon/bookicon.gifPK 5&Apµ*¤c ^ $Ź OEBPS/dcommon/conticon.gifPK 5&A²Źø ³ ĻĶ OEBPS/dcommon/blafdoc.cssPK 5&A+ & Īä OEBPS/dcommon/rightnav.gifPK 5&AjÓ eõ8 š8 Aę OEBPS/dcommon/oracle-small.JPGPK 5&A¤Ž{& ! OEBPS/dcommon/help.gifPK 5&AI>ĘR Z Z
ģ OEBPS/toc.htmPK 5&AŠöÕC >
E{ OEBPS/apc.htmPK 5&AzłEv³ ®
Ć OEBPS/lot.htmPK 5&AŻŚ½ŠŻŌ ÓŌ ± OEBPS/ch10.htmPK A A å Źp
9 Gateway Configuration Using TCP/IP Communication Protocol
9.1 Before You Begin
9.2 Preparing to Configure a Gateway Installation/Upgrade
%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 's Oracle home directory.%ORACLE_HOME%\dg4appc\demo directory. Copy the pgavsn.sql and pgaecho.sql files into a similarly named directory in the Oracle database .pgaims.sql file from the gateway Oracle home %ORACLE_HOME%\dg4appc\demo\IMS directory to your Oracle database 's Oracle home %ORACLE_HOME%\dg4appc\demo\IMS directory.IVTNV and IVTNO, then you will need to copy the ivtno.ctl, ivtnod.sql, ivtnv.ctl, and ivtnvd.sql files into the Oracle database 's Oracle home %ORACLE_HOME%\dg4appc\demo\IMS directory as well. Make sure to generate the required TIPs and transfer them as well.
C:\> echo %ORACLE_HOME%
C:\oracle\pga\11.2
\oracle\pga\11.2' directory, then you need to do the following:
C:\> SET ORACLE_HOME=C:\oracle\pga\11.2
C:\> cd %ORACLE_HOME%
C:\> mkdir dg4appc
C:\> mkdir dg4appc\admin
C:\> mkdir dg4appc\demo
C:\> mkdir dg4appc\demo\IMS
.sql, .pkh, and .pkb files from the gateway's Oracle home %ORACLE_HOME%\dg4appc\admin directory to the Oracle database 's Oracle home %ORACLE_HOME%\dg4appc\admin directory.pgaecho.sql files and directory recursively from the gateway Oracle home's %ORACLE_HOME%\dg4appc\demo directory to the Oracle database 's %ORACLE_HOME%\dg4appc\demo directory.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.IVTNV and IVTNO, then you will need to copy the ivtno.ctl, ivtnod.sql, ivtnv.ctl, and ivtnvd.sql files into the Oracle database 's Oracle home %ORACLE_HOME%\dg4appc\demo\IMS directory as well. Make sure to generate the required TIPs and transfer them as well.
9.3 Configuring the Oracle Database : First Time Installation
UTL_RAW PL/SQL package has been installed on the Oracle database . All PGAU-generated TIP specifications use UTL_RAW, which provides routines for manipulating raw data.
SQL> DESCRIBE UTL_RAW
DESCRIBE statement produces output on the 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.DESCRIBE statement indicates success, then your Oracle database has UTL_RAW installed and you can proceed to StepĀ 2.SYS.prvtrawb.plb scripts in the Oracle database %ORACLE_HOME%\rdbms\admin directory, in the following order:
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @utlraw.sql
SQL> @prvtrawb.sql
DBMS_OUTPUT standard PL/SQL package is enabled on your Oracle database . The sample programs and installation verification programs on the distribution media use this standard package.SYS.
SQL> DESCRIBE DBMS_OUTPUT
DESCRIBE statement produces output on your screen. If you browse through that output, then you should see some functions, including a put_line function.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.DESCRIBE statement indicates success, then your Oracle database has DBMS_OUTPUT created, and you can proceed to StepĀ 3.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.SYS.
SQL> DESCRIBE HS_FDS_CLASS
DESCRIBE statement produces output on the 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.DESCRIBE statement does not indicate success, then you must create Heterogeneous Services catalogs and you must perform StepĀ c below:
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @caths.sql
SYSTEM. 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'
PGAADMIN and install the PG DD.SYSTEM.pgacr8au.sql script in the %ORACLE_HOME%\dg4appc\admin directory. This script creates the PGAADMIN userĀ ID.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgacr8au.sql
PGAADMIN.pgddcr8.sql script in the %ORACLE_HOME%\dg4appc\admin directory. This script installs the PGĀ DD.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddcr8.sql
SYS.DBMS_PIPE to PGAADMIN:
SQL> GRANT EXECUTE ON DBMS_PIPE TO PGAADMIN
pg4tcpmap package has been installed on your Oracle database . Follow StepsĀ a throughĀ c to test for proper installation of pg4tcpmap.pg4tcpmap tool, and refer to Chapter 6 of the Oracle Database Gateway for APPC User's Guide for details about the commands needed to run the tool.SYSTEM.
SQL> select table_name, owner
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, uniqueness
from dba_indexes
where index_name = 'PGA_TCP_IMSC_IND';
SELECT statements must produce one row each. Following is the result for the first select statement:
TABLE_NAME OWNER
------------------------------ ------------------------------
PGA_TCP_IMSC PGAADMIN
OWNER INDEX_NAME TABLE_NAME UNIQUENESS
---------- ------------------ -------------- ---------
PGAADMIN PGA_TCP_IMSC_IND PGA_TCP_IMSC UNIQUE
pgaimsc.sql script in the Oracle database 's %ORACLE_HOME%\dg4appc\admin directory:
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgaimsc.sql
DBMS_PIPES standard PL/SQL package is installed and that PGAADMIN has execute privileges on it. For more information about DBMS_PIPES, refer to the Oracle Database Rules Manager and Expression Filter Developer's Guide.PGAADMIN.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgatiptr.sql
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").PGAADMIN.gpglocal.pkh script in the %ORACLE_HOME%\dg4appc\admin directory. This script compiles the GPGLOCAL package specification.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @gpglocal.pkh
gpglocal.pkb script in the %ORACLE_HOME%\dg4appc\admin directory. This script compiles the GPGLOCAL package body.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @gpglocal.pkb
NLS_LANGUAGE and Side Profile Settings. Specify the suitable ASCII character set in the DEFINE TRANSACTION command.
9.4 Upgrading or Migrating the Oracle Database from Previous Gateways
SYS.UTL_RAW package body. From SQL*Plus, run the prvtrawb.plb script from the %ORACLE_HOME%\rdbms\admin directory. This script upgrades the UTL_RAW package body.
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @prvtrawb.plb
UTL_PG package body. From SQL*Plus, run the prvtpgb.plb script from the %ORACLE_HOME%\rdbms\admin directory. This script upgrades the UTL_PG package body.
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @prvtpgb.plb
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 Section 9.4.1, "If You Must Reinstall Package Specifications".
9.4.1 If You Must Reinstall Package Specifications
UTL_RAW or UTL_PG package has been invalidated or removed, then the prvtrawb.plb and prvtpgb.plb scripts may not complete successfully, then, you might have to reinstall the package specifications.
%ORACLE_HOME%\dg4appc\admin directorySYS.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:
C:\> cd %ORACLE_HOME%\rdbms\admin
SQL> @utlraw.sql
SQL> @utlpg.sql
UTL_RAW and UTL_PG package body
9.4.2 Upgrading PGAU from Previous Gateway Releases
PGAADMIN.pgddupgr.sql script in the %ORACLE_HOME%\dg4appc\admin directory. This script upgrades the PG DD.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddupgr.sql
9.5 Optional Configuration Steps to Permit Multiple Users
PGAADMIN to perform PG DD operations using PGAU.PGAADMIN user can grant these roles to other users as necessary.PGAADMIN.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddcr8r.sql
C:\> 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
C:\> 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>ÓT,« GRANT EXECUTE ON PGAADMIN.GPGLOCAL TO PUBLIC;
SQL> EXIT
%ORACLE_HOME%\dg4appc\admin directory. The pgddapub.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's userĀ ID:PGAADMIN.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.
C:\> cd %ORACLE_HOME%\dg4appc\admin
SQL> @pgddapub.sql
SQL> @pgddadev.sql
GENERATE statement.
C:\> pgau
PGAU> CONNECT PGAADMIN\pgaadmin@database_specification_string
PGAU> GENERATE tranname
PGAU> EXIT
GENERATE command, refer to the PGAU GENERATE section in Chapter 2 of the Oracle Database Gateway for APPC User's Guide.
C:\> sqlplus tip_owner\pw@database_specification_string
SQL> @tipname.pkh
SQL> @tipname.pkb
SQL> exit
GENERATE produces the TIP in two output files, a specification and a body. You must compile both, first the specification and then the body.GENERATE command, refer to the PGAU GENERATE command section in Chapter 2 of the Oracle Database Gateway for APPC User's Guide.
9.6 Configuring TCP/IP for the Gateway
9.7 Configuring the Gateway
initsid.ora, which is in the %ORACLE_HOME%\dg4appc\admin directory. A sample gateway parameter file, initPGA.ora, is provided in this subdirectory.
initsid.ora file, substitute your gateway SID name for "sid " in this file name.
initsid.ora file by deleting the APPC parameters. Refer to Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol" for the valid TCP/IP parameters.
PGA_CAPABILITY parameter.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.
9.8 Loading the PGA_TCP_IMSC Table
pg4tcpmap tool.pg4tcpmap tool resides 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).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.pg4tcpmap, you must specify the ORACLE_HOME, Oracle SID and modify initsid.ora. Refer to Appendix B, "Gateway Initialization Parameters for TCP/IP Communication Protocol" in this guide and Chapter 6 in the Oracle Database Gateway for APPC User's Guide for complete information about the pg4tcpmap commands.pg4tcpmap commands and instructions for using them, as well as an example of the table. Refer to "Troubleshooting" in the Oracle Database Gateway for APPC User's Guide for information about the trace file for the executed pg4tcpmap tool.
C:\> cd %ORACLE_HOME%\bin
C:\> pg4tcpmap
pg4tcpmap output.
9.9 Verifying the Gateway Installation and OLTP Configuration
.sql files to give them the particular database link name that you created in Step 5 of "Configuring the Oracle Database : First Time Installation". You must modify the following .sql files:
9.9.1 Verifying the Gateway Installation
PGAADMIN.%ORACLE_HOME%\dg4appc\demo\pgavsn.sql.
C:\> cd %ORACLE_HOME%\dg4appc\demo
SQL> @pgavsn.sql
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.
%ORACLE_HOME%\dg4appc\demo\pgaecho.sql.
C:\> cd %ORACLE_HOME%\dg4appc\demo
SQL> @pgaecho.sql
==> Congratulations, your installation was successful. <==
9.9.2 Verifying the OLTP Configuration
9.9.2.1 IMS/TM Verification
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 the IMS/TM system for the gateway):
FLIP THIS MESSAGE
EGASSEM SIHT PILF
pgaims.sql file, which resides 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:PGAADMIN.
C:\> cd %ORACLE_HOME%\dg4appc\demo\IMS
SQL> @pgaims.sql
==> Congratulations, your gateway is communicating with IMS/TM <==
9.10 Performing Postinstallation Procedures
9.10.1 Installing Sample Applications
ivtno.ctl and ivtnv.ctl.
%ORACLE_HOME%\dg4appc\demo\IMS\ivtno.ctl and%ORACLE_HOME%\dg4appc\demo\IMS\ivtnv.ctl files.IVTNO and IVTNV sample transactionsREADME.doc files in the following directory:%ORACLE_HOME%\pg4appc\demo\IMS\sample_IMS_applications.txt