13 Configuring the DRDA Server
This section describes tasks you must perform to configure the DRDA server. Each supported operating system is addressed separately. Experience with the given operating system and database is required.
The steps for configuring your remote DRDA server apply to the following DRDA servers:
-
DB2 UDB for z/OS
-
DB2 UDB for iSeries
-
DB2 UDB for Linux, UNIX, and Windows
Configuring a DRDA database to enable access by the gateway requires actions on the DRDA database 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 DRDA database are required during the configuration. Refer to the vendor documentation for complete information about your host system and DRDA database.
Topics:
13.1 Configuring the DRDA Server for DB2 UDB for z/OS
Perform the following tasks to configure the DRDA server with DB2 on a z/OS system:
Parent topic: Configuring the DRDA Server
13.2 Configuring the DRDA Server for DB2 UDB for iSeries
Experience with DB2 UDB for iSeries and AS/400 is required to perform the following steps:
Parent topic: Configuring the DRDA Server
13.3 Configuring the DRDA Server for DB2 UDB for Linux, UNIX, and Windows
Experience with DB2/UDB, configuring the communication subsystem of DB2 UDB for Linux, UNIX, and Windows, and the host System Administration tools is required to perform the following steps.
Parent topic: Configuring the DRDA Server
13.4 Manual Binding of DRDA Gateway Packages
The gateway uses several DB2 packages, which it normally uploads and binds during the first time the gateway connects to a DB2 instance. In some customer environments, the connecting userid may not have the necessary privileges to perform the binding, or some customers may prefer to manually bind the packages rather than allow the gateway to do the binding.
In such cases, Oracle provides a predefined set of packages for manual binding. These packages come with several restrictions that must be observed by setting specific gateway initialization parameters to set values otherwise, the gateway will attempt to rebind the package automatically.
This section contains the following sub-sections:
- Manually Binding of Packages for DB2 UDB for z/OS
- Manually Binding of Packages for DB2 UDB for Linux, Unix, and Windows
Parent topic: Configuring the DRDA Server
13.4.1 Manually Binding of Packages for DB2 UDB for z/OS
Perform the following steps to manually bind packages for DB2 UDB for z/OS:
To use these packages with the gateway, please set the following init parameters in the gateway initialization file:
-
HS_OPEN_CURSORS=200
-
HS_FDS_PACKAGE_COLLID=NULLID
Parent topic: Manual Binding of DRDA Gateway Packages
13.4.2 Manually Binding of Packages for DB2 UDB for Linux, Unix, and Windows
Perform the following steps to manually bind packages for DB2 UDB for Linux, Unix, and Windows:
To use these packages with the gateway, set the following initialization parameters in the gateway initialization file:
-
HS_OPEN_CURSORS=200
-
HS_FDS_PACKAGE_COLLID=NULLID
Parent topic: Manual Binding of DRDA Gateway Packages