To access a remote database server through IPX/SPX, you must first have installed and configured communication software for both the client and DB2 server workstations. See "Software Requirements" for the communication protocol requirements for your platform. See "Possible Client-to-DB2 Server Connectivity Scenarios" for the supported communication protocols for your particular client and server.
Before completing the steps in this section, be sure that you have completed the instructions in "Setting the DB2COMM Registry Value".
If you are setting up communications for the Administration Server, it was configured for IPX/SPX (using the registered Socket number 87A2) when it was created. There are no further steps required to enable the Administration Server to use IPX/SPX.
Your DB2 server can be set up to support IPX/SPX client communications via Direct Addressing or File Server Addressing.
See Table 25 for a list of the supported IPX/SPX addressing methods for your
server.
Table 25. IPX/SPX Supported Communication Methods for a DB2 Server
Server Platform | Direct Addressing | File Server Addressing |
AIX | * | * |
HP-UX | * | * |
Solaris | * |
|
The following steps are required to set up IPX/SPX communications:
As you proceed through the configuration steps, complete the Your
Value column in the following table. You can fill in some of the
values before you start configuring this protocol.
Table 26. IPX/SPX Values Required at the Server
Parameter | Explanation | Our Example | Your Value |
---|---|---|---|
File server name (FILESERVER) |
|
| |
DB2 server object name (OBJECTNAME) |
|
| |
Socket number (IPX_SOCKET) | Represents the connection end point in a DB2 server's internetwork
address. It must be unique for all server instances, and all IPX/SPX
applications running on the workstation. It is entered in hexadecimal
format.
DB2 has registered well known sockets with Novell in the range 0x879E to 0x87A1. If you run more than 4 instances on the server machine, you must prevent socket collisions for instances 5 and up by choosing a socket number that is not 0x0000, in the dynamic socket range 0x4000 to 0x7FFF, or in the range 0x8000 to 0x9100 (these are well known sockets that are registered to various applications). The maximum value for this parameter is 0xFFFF. | 879E (default) | |
IPX/SPX Internetwork Address | The internetwork address required when configuring a client to communicate with a server using Direct Addressing. | 09212700.400011527745.879E |
|
The following steps describe how to configure this protocol on the server. Replace the sample values with your values and record them on your worksheet.
You must update the database manager configuration file with the File server (FILESERVER), DB2 server object name (OBJECTNAME), and Socket number (IPX_SOCKET) parameters.
To update the database manager configuration file, perform the following steps:
![]() |
If you have trouble logging on to the system, see "Logging on to the System".
|
. INSTHOME/sqllib/db2profile (for Bourne or Korn shell) source INSTHOME/sqllib/db2cshrc (for C shell)where INSTHOME is the home directory of the instance
update dbm cfg using fileserver FILESERVER objectname OBJECTNAME ipx_socket IPX_SOCKET db2stop db2start
For example, if you have chosen a value of 879E for the Socket number (IPX_SOCKET) parameter, use:
update dbm cfg using fileserver * objectname * ipx_socket 879E db2stop db2start
For example, if the name of the File server (FILESERVER) is NETWSRV, the DB2 server's object name (OBJECTNAME) is DB2INST1, and you have chosen a value of 879E for the Socket number (IPX_SOCKET) parameter, use:
update dbm cfg using fileserver NETWSRV objectname DB2INST1 ipx_socket 879E db2stop db2start
View the database manager configuration file, to ensure that these changes have taken effect, by issuing the following command in the command line processor:
get database manager configuration
![]() |
If you are planning to only support clients that use Direct Addressing, you will be required to enter the server's IPX/SPX internetwork address as the DB2 server object name when cataloging the node on the client. Determine the value for the OBJECTNAME parameter by issuing the db2ipxad command on the server. This command is located in the sqllib/misc/ directory. Make note of this output on your worksheet for use when you configure an
IPX/SPX client using the command line processor.
|
![]() |
If you are planning to support clients using only Direct Addressing, you
are now finished the configuration and are ready to install a DB2
client. Go to Chapter 7. "Installing DB2 Clients" for more information.
|
The DB2 server must be registered after the database manager configuration file has been updated with the IPX/SPX parameters. To register the DB2 server instance at the NetWare File server, issue the following command in the command line processor:
register db2 server in nwbindery user USERNAME password PASSWORD
Notes:
![]() |
Now that you have configured the server, you are ready to install a DB2
client. Go to Chapter 7. "Installing DB2 Clients" for more information.
|