Skip Headers
Oracle® Database Gateway for APPC Installation and Configuration Guide
11g Release 1 (11.1) for AIX 5L Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), Solaris Operating System (SPARC 64-Bit), and Linux x86

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

Go to previous page
Previous
Go to next page
Next
View PDF

B Gateway Initialization Parameters for TCP/IP Communication Protocol

This appendix describes the parameters needed for a gateway featuring the TCP/IP for IMS Connect communication protocol. It also provides a sample output of the pg4tcpmap tool. In addition, this appendix contains sample listener.ora and tnsnames.ora files for a ­gateway using TCP/IP. It contains the following sections:

B.1 Gateway Initialization Parameter File Using TCP/IP

The parameter file for the Oracle Database Gateway for APPC using TCP/IP for IMS Connect is located in the $ORACLE_HOME/dg4appc/admin directory and is called initsid.ora.

Note:

The initsid.ora file contains both SNA and TCP/IP parameters. You will need to modify these files with the suitable parameters.

B.1.1 PGA Parameters

The PGA parameters control the TCP/IP interface portion of the gateway. PGA parameters are specified using the 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

LOG_DESTINATION=logpath

logpath specifies the destination at which STDERR is reopened. LOG_DESTINATION specifies a directory only and STDERR is reopened to logpath/sid_pid.log

where:

  • sid is the sid name

  • pid is the process ID assigned to the gateway

NOTE: This parameter will be used for the pg4tcpmap tool when you set the Trace Level to 255. The log file for this tool will reside in the same place as the gateway log file, in pg4tcpmap_sid.log.

PGA_CAPABILITY

PGA transaction capability. The following are valid values:

READ_ONLY or RO: Read-only capabilities.

SINGLE_SITE or SS: Single-site update only. This indicates that in a distributed environment, only the gateway can perform updates. No other database updates can occur within the Oracle transaction.

The default is SINGLE_SITE.

PGA_SECURITY_TYPE

TCP/IP conversation security option. This controls what security parameters are sent to the OLTP. The following are valid values:

NONE: Sends no security parameters

PROGRAM: Sends a user ID and password

The default is NONE.

For further information on these options, refer to Chapter 14, "Security Requirements".

Important: You must specify your RACF group name through the pg4tcpmap tool if you have set your PGA security option to SECURITY=PROGRAM. For more information about this issue, refer to the Oracle Database Gateway for APPC User's Guide.

If you have already loaded the table pga_tcp_imsc and you did not first specify the RACF group name, delete the row and reinsert it with the value for the RACF group name.

PGA_TCP_DB

The Oracle Net service name for the Oracle database in which the gateway receives its TCP/IP for IMS Connect information, such as host name and port number. This parameter can be from 1 to 255 characters long. This parameter is required.

There is no default value.

PGA_TCP_PASS

The Oracle password to be used by the gateway when connecting to the Oracle database specified by the PGA_TCP_DB parameter. The password can be from 1 to 30 characters long. This parameter is required. The password can be encrypted. For more information about encrypting the password, refer to Passwords in the Gateway Initialization File.

There is no default value.

PGA_TCP_USER

The Oracle user ID to be used by the gateway when connecting to the Oracle database specified by the PGA_TCP_DB parameter. The user ID can be from 1 to 30 characters long. This parameter is required.

There is no default value.

TRACE_LEVEL

PGA trace level. This controls tracing output written to STDERR (the target of the LOG_DESTINATION parameter). The value must be an integer from 0 to 255.

The default is 0, indicating no tracing.

NOTE: This parameter is used in the pg4tcpmap tool as well as the gateway.


B.2 Output for the pg4tcpmap Tool

The following output illustrates the results from executing the pg4tcpmap tool when running TCP/IP for IMS Connect on the gateway. Refer to Section 13.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 angle brackets (<>).

$ pg4tcpmap

PG4TCPMAP: Release 11.1.0.6 - Production on Fri Jun 3 14:57:41 2007

Copyright(c) 1982,2007 Oracle.  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.
pgaimst
Enter either the remote hostname or its TCP/IP address.
<mvs08>
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 goup name? (Y|N)
If NO, the default is blank.
<n>
Requested to INSERT a row.
'Side Profile name' is 'PGAIMST'
'remote host name' is 'MVS08'
'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 '        '
pg4tcpmap is complete.

B.2.1 Sample listener.ora File for a Gateway Using TCP/IP

The following is an example of a listener.ora file for a gateway using TCP/IP:

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 = /oracle/pga/11.1)
      (PROGRAM = pg4t4ic)
    )
  )

B.2.2 Sample tnsnames.ora File for a Gateway Using TCP/IP

The following is an example of a tnsnames.ora file for a gateway using TCP/IP:

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)
  )