Quick Beginnings for DB2 Extended Enterprise Edition for UNIX

Configuring IPX/SPX on the Server

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.

In Direct Addressing, the client connects to the DB2 server by directly specifying the IPX/SPX internetwork address of the server (bypassing the NetWare file server). Using this method, a NetWare file server is not required on the network. Configure DB2 servers using this addressing method if they will be accessed solely by clients using Direct Addressing.

The following steps are required to set up IPX/SPX communications:

Identify and record parameter values.
Configure the server:
1. Update the database manager configuration file.

Step 1. Identify and Record Parameter Values

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 19. IPX/SPX Values Required at the Server

Parameter Explanation Our Example Your Value
File server name (FILESERVER)
A * value indicates that you are using Direct Addressing.
*
DB2 server object name (OBJECTNAME)
A * value indicates that you are using Direct Addressing.

*

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

Parameter	Explanation	Our Example
File server name (`FILESERVER`)	A `*` value indicates that you are using Direct Addressing.	`*`
DB2 server object name (`OBJECTNAME`)	A `*` value indicates that you are using Direct Addressing.	`*`
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`

Step 2. Configure the Server

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.

A. Update the Database Manager Configuration File

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:

Log on to the system as a user with System Administrative (SYSADM) authority.

If you have trouble logging on to the system, see "Logging on to the System".
Set up the instance environment and invoke the DB2 command line processor as follows:
1. Run the start up script as follows:
```
   . INSTHOME/sqllib/db2profile    (for Bourne or Korn shell)
   source INSTHOME/sqllib/db2cshrc (for C shell)
```
  where INSTHOME is the home directory of the instance.
2. Start the DB2 command line processor by issuing the db2 command.
In the database manager configuration file, update the File server (FILESERVER), DB2 server object name (OBJECTNAME), and Socket number (IPX_SOCKET) parameters using the following commands in the command line processor:
```
   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
```

After the database manager is stopped and started again, view the database manager configuration file to ensure that these changes have taken effect. Enter 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 8. "Installing DB2 Clients" for more information.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]