Release 9.0.1.0.1 for Sun Solaris
Part Number A90399-01
 Library |
 Product |
 Contents |
 Index |
| Oracle Transparent Gateway for IBM DRDA Installation and User's Guide Release 9.0.1.0.1 for Sun Solaris Part Number A90399-01 |
|
This appendix contains the DRDA-specific parameters defined in the Gateway Initialization File and the Startup Shell Script. Read and understand the information on each parameter, taking special note of parameters that have defaults that do not apply to your system:
If you change any parameters in the Gateway Initialization File, you must stop and re-start the Gateway in order for them to take effect. If you change certain parameters, then you must also rebind the DRDA package. Any parameters that affect the DRDA package have a note in their description that rebinding is required.
Parameters specific to the gateway are stored in the Gateway Initialization File, initsid.ora.
Parameters and their values are specified using the following form:
drda_parameter = value
where:
drda_parameter is on the DRDA parameters
value is a character string with contents dependent on the drda_parameter
Below is a list of gateway initialization file parameters and their descriptions.
Default value: none
Range of values: Refer to "Native Semantics"
Syntax: DRDA_CAPABILITY={FUNCTION/{ON|OFF}},...
DRDA_CAPABILITY specifies which Oracle mapped functions will be treated natively. In other words, no special pre/post processing will be done for these functions. They will be passed through to the DRDA server unmodified.
Default value: codepage.map
Range of values: any valid file path
Syntax: DRDA_CODEPAGE_MAP=codepage.map
DRDA_CODEPAGE_MAP specifies the location of the codepage map. You may specify only the filename, which will be searched for within the $ORACLE_HOME/tg4drda/admin directory, or you may specify the full path name of the file.
Default value: 32767
Range of values: 512 through 32767
Syntax: DRDA_COMM_BUFLEN=num
DRDA_COMM_BUFLEN specifies the communications buffer length. This is a number indicating the size of the SNA send/receive buffer in bytes.
Default value: DRDACON1
Range of values: any alphanumeric string 1 to 8 characters in length
Syntax: RDA_CONNECT_PARM=name
For Version 9.0, the name of the Side Information File is specified as DRDA_CONNECT_PARM=/oracle/tg4drda/side9/DB2V23LU. For more information, refer to Chapter 5, "Oracle Net".
Default value: DRDACON1:446
Range of values: Any alphanumeric string 1 to 255 characters in length
Syntax: DRDA_CONNECT_PARM={hostname|ip_address}{:port}
DRDA_CONNECT_PARM specifies the TCP/IP hostname or IP Address of the DRDA server and, as an option, the Service Port number on which the DRDA server is listening.
Default value: FALSE
Range of values: {TRUE |FALSE}
Syntax: DRDA_CMSRC_CM_IMMEDIATE={TRUE|FALSE}
DRDA_CMSRC_CM_IMMEDIATE sets the SNA session allocation mode. A setting of FALSE will cause the gateway to wait for a free session if no free sessions exist. A setting of TRUE will cause the gateway to fail the allocation immediately if no free sessions exist.
Default value: none
Range of values: any supported DRDA server CCSID
Syntax: DRDA_DEFAULT_CCSID=ccsid
DRDA_DEFAULT_CCSID specifies the default CCSID or character set codepage for character set conversions when the DRDA server database indicates that a character string has a CCSID of 65535. DRDA servers use CCSID 65535 for columns specified as "FOR BIT DATA". In most cases, this parameter should not be specified, allowing CCSID 65535 to be treated as an Oracle RAW datatype.
This parameter is for supporting databases (in particular, DB2/400) that use CCSID 65535 as the default for all tables created. Allowing CCSID 65535 to be treated as another CCSID can save such sites from having to modify every table.
Default value: TRUE
Range of values: {TRUE|FALSE}
Syntax: DRDA_DESCRIBE_TABLE={TRUE|FALSE}
DRDA_DESCRIBE_TABLE directs the gateway to use the DRDA operation "Table Describe" to return the description of tables. This is an optimization that reduces the amount of time and resources that are used to look up the definition of a table.
Default value: TRUE
Range of values: {TRUE|FALSE}
Syntax: DRDA_DISABLE_CALL={TRUE|FALSE}
DRDA_DISABLE_CALL controls stored procedure usage, and is also used to control how the package is bound on the target database. The gateway supports execution of stored procedures only on IBM DB2/MVS Version 4.1 or above and DB2/400 Version 3.1. Use the value, FALSE, only if the target database is DB2/MVS Version 4.1 or DB2/400 Version 3.1. Set this parameter to TRUE for all other target databases.
Default value: SESSION
Range of values: {SESSION|COMMIT}
Syntax: DRDA_FLUSH_CACHE={SESSION|COMMIT}
DRDA_FLUSH_CACHE specifies when the cursor cache is to be flushed. With DRDA_FLUSH_CACHE=COMMIT, the cursor cache is flushed whenever the transaction is committed. With DRDA_FLUSH_CACHE=SESSION, the cache is not flushed until the session terminates.
Default value: CHG for DB2/400, CS for DB2/MVS, DB2/UDB, DB2/VM
Range of values: {CHG|CS|RR}
Syntax: DRDA_ISOLATION_LEVEL={CHG|CS|RR}
DRDA_ISOLATION_LEVEL specifies the isolation level defined to the package when it is created. All SQL statements sent to the remote DRDA database are executed with this isolation level. Isolation level seriously affects performance of applications. Use caution when specifying an isolation level other than the default. For information on isolation levels, refer to your IBM database manuals.
The following table lists the isolation levels and their descriptions. The levels are specified in ascending order of control, with CHG having the least reliable cursor stability and RR having the most. Note that higher stability uses more resources on the server and can lock those resources for extended periods.
| Level | Description |
|---|---|
|
CHG |
Change (default for DB2/400) |
|
CS |
Cursor Stability (default for DB2/UDB, DB2/MVS, and DB2/VM) |
|
RR |
Repeatable Read |
Default value: AIX_RS6K
Range of values: any alphanumeric string 1 to 8 characters in length.
Syntax: DRDA_LOCAL_NODE_NAME=name
DRDA_LOCAL_NODE_NAME specifies the name by which the gateway will be known to the DRDA server. This name is used internally by the DRDA server to identify the local node.
Default value: TRUE
Range of values: {TRUE|FALSE}
Syntax: DRDA_OPTIMIZE_QUERY={TRUE|FALSE}
DRDA_OPTIMIZE_QUERY turns on or off the distributed query optimizer (DQO) capability. Refer to "Performing Distributed Queries" in Chapter 9, "Using the Gateway". The DQO capability is useful for optimizing queries that access large amounts of data, but it can add overhead to small queries.
This parameter is valid only if your DRDA server is DB2/MVS or DB2/VM. If your DRDA server is DB2/400 or DB2/UDB, then you must set the value to FALSE.
Default value: none
Range of values: any valid CCSID
Syntax: DRDA_OVERRIDE_FROM_CODEPAGE=ccsid
DRDA_OVERRIDE_FROM_CODEPAGE, when used together with DRDA_OVERRIDE_TO_CODEPAGE, provides a method of forcing a certain character set codepage or CCSID to be substituted for an unsupported codepage within the DRDA server database. This parameter should be used only if you get one of the following errors when using the gateway:
ORA-1460 : unimplemented or unreasonable conversion DRDA: drc=865B,gdc=-332,inf=0001,sqlcode=0,sqlstate=57017,errp=GDJREACS DRDA: errmc=xxx850 DRDA: errd=865B,0,0,0,0,0
where xxx is the unsupported CCSID.
Set DRDA_OVERRIDE_FROM_CODEPAGE to the unsupported codepage (xxx), and set DRDA_OVERRIDE_TO_CODEPAGE to a compatible codepage. Use caution when setting these parameters because they cause an incorrect codepage to be used for character translation, and certain characters in the data will be translated incorrectly. Refer to Appendix D, "National Language Support", for information on supported codepages.
This parameter is deprecated and will be removed in a future release of the gateway. Use the Codepage Map Facility.
Default value: none
Range of values: Any valid CCSID
Syntax: DRDA_OVERRIDE_TO_CODEPAGE=ccsid
DRDA_OVERRIDE_TO_CODEPAGE, when used together with DRDA_OVERRIDE_FROM_CODEPAGE, provides a method of forcing a certain character set codepage or CCSID to be substituted for an unsupported codepage within the DRDA server database. Set DRDA_OVERRIDE_TO_CODEPAGE to a compatible and supported codepage. For more information, refer to the section, "DRDA_OVERRIDE_FROM_CODEPAGE (obsolete)". Refer to Appendix D, "National Language Support", for information on supported codepages.
This parameter is deprecated and will be removed in a future release of the gateway. Use the Codepage Map Facility.
Default value: ORACLE
Range of values: an alphanumeric string 1 to 18 characters in length
Syntax: DRDA_PACKAGE_COLLID=collection_id
DRDA_PACKAGE_COLLID specifies the package collection ID.
Default value: none, use the sample provided
Range of values: a 16-digit hexadecimal number
Syntax: DRDA_PACKAGE_CONSTOKEN=hexnum
DRDA_PACKAGE_CONSTOKEN specifies the package consistency token. This is a 16-digit hexadecimal representation of an 8-byte token. Oracle Corporation recommends that you do not change the consistency token. The consistency token used at runtime must match the one used when the package is bound. The value depends on the DRDA server being used.
Default value: G2DRSQL
Range of values: an alphanumeric string 1 to 18 characters in length
Syntax: DRDA_PACKAGE_NAME=name
DRDA_PACKAGE_NAME specifies the package name.
Default value: none
Range of values: any valid user ID
Syntax: DRDA_PACKAGE_OWNER=userid
DRDA_PACKAGE_OWNER specifies the database user ID that owns the package. This allows the owner to be a user other than the connected user ID when the package is created. The package owner must be the same user as the owner of the ORACLE2PC table. This is not valid for DB2/VM.
Default value: 100
Range of values: any integer between 1 and 65535
Syntax: DRDA_PACKAGE_SECTIONS=num
DRDA_PACKAGE_SECTIONS specifies the number of cursors declared at the remote database when the package is bound. This is the maximum number of open cursors allowed at any one time. Change this parameter only if an application needs more than 100 open concurrent cursors.
This parameter has become obsolete. Refer to parameters "FDS_CLASS" and "FDS_INSTANCE" later in this chapter.
Default value: none
Range of values: {any valid password
Syntax: DRDA_RECOVERY_PASSWORD=passwd
DRDA_RECOVERY_PASSWORD is used with the DRDA_RECOVERY_USERID. The recovery user connects to the IBM database if a distributed transaction is in doubt. For more information, refer to "Two-Phase Commit Processing".
Default value: FALSE
Range of values: {TRUE|FALSE}
Syntax: DRDA_READ_ONLY={TRUE|FALSE}
DRDA_READ_ONLY specifies whether the gateway runs in a read-only transaction mode. In this mode, SQL statements which modify data are not allowed.
Default value: ORARECOV
Range of values: any valid user ID
Syntax: DRDA_RECOVERY_USERID=userid
DRDA_RECOVERY_USERID specifies the user ID that is used by the gateway if a distributed transaction becomes in doubt. This use ID must have execute privileges on the package and must be defined to the IBM DRDA database.
If a distributed transaction becomes in doubt, then the integrating Oracle Server determines the status of the transaction by connecting to the IBM DRDA database, using the DRDA_RECOVERY_USERID. If this parameter is missing, the gateway attempts to connect to a user ID of ORARECOV. For more information, refer to "Two-Phase Commit Processing".
Default value: DB2V2R3
Range of values: an alphanumeric string 1 to 18 characters in length
Syntax: DRDA_REMOTE_DB_NAME=name
DRDA_REMOTE_DB_NAME specifies the DRDA server location name. This is an identifying name assigned to the server for DRDA purposes. A technique for determining this name using a SQL SELECT statement is discussed in each of the server-specific installation sections in Chapter 6, "Configuring the DRDA Server".
Default value: PROGRAM
Range of values: {PROGRAM|SAME}
Syntax: DRDA_SECURITY_TYPE={PROGRAM|SAME}
DRDA_SECURITY_TYPE specifies the type of security used for SNA communications. For more information about types of security and about setting DRDA_SECURITY_TYPE, refer to Chapter 11, "Security Considerations".
Default value: $ORACLE_HOME/tg4drda/log/gateway sid_pid.log
Range of values: any valid file path
Syntax: LOG_DESTINATION=logpath; export LOG_DESTINATION
LOG_DESTINATION specifies the destination for gateway logging and tracing. This parameter should specify a file. If the file already exists, it will be overwritten.
After any failure to open the logpath, a second attempt to open the default is made.
Usually, LOG_DESTINATION should specify a directory. If it is specified as a file, and if two or more users simultaneously use the same instance of the gateway, then they are writing to the same log. The integrity of this log is not guaranteed. If you do not specify this parameter, then the default is assumed.
Default value: 4712-12-31
Range of values: any valid date less than 4712-12-31
Syntax: ORA_MAX_DATE=yyyy-mm-dd
ORA_MAX_DATE specifies the gateway maximum date value. If the fetched date value is larger than 4712-12-31, the gateway replaces the date value with the value defined by the ORA_MAX_DATE parameter. Any date between January 1, 4712 BC and December 31, 4712 AD is valid.
Default value: none
Range of values: any valid file path
Syntax: ORACLE_DRDA_TCTL=tracecontrolpath
ORACLE_DRDA_TCTL specifies the path to the DRDA internal trace control file. This file contains module tracing commands. A sample file is stored in $ORACLE_HOME/tg4drda/admin/debug.tctl. This parameter is used for diagnostic purposes.
Default value: value specified for LOG_DESTINATION
Range of values: any valid file path
Syntax: ORACLE_DRDA_TRACE=logpath
ORACLE_DRDA_TRACE is used to specify a different log path for DRDA internal tracing. This tracing is separate from the rest of the gateway tracing, as specified by the LOG_DESTINATION parameter. By default, this parameter will append the DRDA internal trace to the gateway trace. This parameter is used for diagnostic purposes.
Default Value: 0
Range of values: 0-255
Syntax: TRACE_LEVEL=number; export TRACE_LEVEL
TRACE_LEVEL specifies a code tracing level. This value determines the level of detail which is logged to the gateway's logfile during execution. This parameter is primarily used for diagnostics.
The parameters in the Startup Shell Script are not order dependent. The syntax of setting parameters is that of the UNIX Bourne shell.
Default value: TG4DRDA_DB2MVS
Range of values: Refer to the table below for a list of valid values
Syntax: FDS_CLASS='TG4DRDA_DB2MVS' ; export FDS_CLASS
FDS_CLASS specifies the capability classification used by Oracle 9i and the gateway. These values might change from release to release, depending on whether the gateway capabilities change.
The valid values for FDS_CLASS are as follows:
Default value: 1
Range of values: {1
Syntax: FDS_CLASS_VERSION=1; EXPORT FDS_CLASS_VERSION
FDS_CLASS_VERSION specifies the version of the FDS_CLASS capabilities. Do not specify this parameter unless directed to do so by Oracle Support Services.
Default value: DRD1
Range of values: the name of the gateway SID
Syntax: FDS_INSTANCE='drdahoa1' ; export FDS_INSTANCE
FDS_INSTANCE specifies a subset of the FDS_CLASS capabilities that may be modified by the user, based on initialization file parameters. If you do not specify this parameter, then it's value will be the Oracle SID defined in the TNS Listener entry.
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|