NetBIOS properties
TCP/IP properties
IPX/SPX properties
Named Pipe properties
APPC properties
NetBIOS properties
TCP/IP properties
IPX/SPX properties
Named Pipe properties
APPC properties
Type the server's workstation name, that is used for this instance, in the workstation name field. This is the nname value stored in this instance's database manager configuration file. The nname that you specify must be unique on the network.
Database clients that connect through NetBIOS use this name to access databases created in this instance. If you change the name specified here, all clients that access databases in this instance must catalog them again.
In the adapter number box, select the LAN adapter that is used on this system for this connection.
The host name is displayed for information only; it applies to the system and cannot be changed through DB2.
In the service name field, enter a service name that will be used in the services file to map the port number that is used for this server instance.
In the port number field, enter the TCP/IP port number that will be used by this server instance to listen for connection requests from clients.
You can setup IPX/SPX support for two different types of addressing, depending on the DB2 server that you run:
Configure this type of addressing if the DB2 server will be accessed by clients using only direct addressing.
Configure this type of addressing if the DB2 server will be accessed by clients using:
or
| Note: | For file server addressing, the following characters are not valid for the file server or object name parameters: / \ : ; , * ? |
The NetWare information that you need is as follows:
| Note: | The file server and object name parameters must be entered in upper case. The following characters are not valid for the file server and object name parameters: /\:;,*? |
The following is a brief description of the items you might need.
The internetwork address of the database manager is stored in the bindery at the NetWare file server.
The socket number defaults to 0x879E (change this value if running more than 1 DB2 server instance). DB2 has registered well-known sockets with Novell in the range 0x879E to 0x87A1 for the customer's use.
The socket number (ipx_socket) must be unique for every DB2 server instance on a machine. It must also be unique among all IPX/SPX applications running on the DB2 server machine to ensure that the DB2 server is able to listen to incoming IPX/SPX connections using this socket number.
The computer name is displayed for information only; it applies to the system and cannot be changed through DB2.
The combination of the computer name and the instance name uniquely identify a DB2 server instance.
Transaction program
In the transaction program name field, enter the name of the transaction program that will be executed when a client connects to this server instance using the APPC protocol.
If DB2 detects an APPC stack that it can configure, then you can enter the information that is needed, and DB2 will configure it. If it has been configured already, you are allowed to change only the LU name.
For DB2 to configure the APPC stack, you must provide the following information.
| Note: | The following fields will only appear if DB2 detected an APPC stack. |
Network ID
Enter the name of the network to which the server is connected. This name is used to identify the network for system management and problem determination.
The network name can be 1 to 8 alphanumeric characters. The special characters @, #, or $ are also allowed; the first character cannot be numeric.
Control Point
Enter the control point name of the server; this is also known as the physical unit (PU) name.
The PU name can be 1 to 8 alphanumeric characters.
Local LU
Enter the logical unit (LU) name of the server.
The LU name can be 1 to 8 alphanumeric characters. The special characters @, #, or $ are also allowed; the first character cannot be @.
Select the Use as default check box if you want this LU to be used as the default LU for the server.
Node ID
The node ID might be optional, depending on how communications are set up on the server. It consists of two parts:
This is the first part of the XID. It contains 3 hexadecimal characters.
This value depends on the communications product used on the database server. For communications products on Intel platforms, the Node ID Block value is conventionally set to 05D.
This is the second part of the XID, it contains 5 hexadecimal characters. It is assigned at the server and used to identify your workstation.
If your server does not require that you assign a node ID, then leave the Node ID blank or set it to 05D 00000.