Quick Beginnings for DB2 Connect Enterprise Edition

Configuring NetBIOS on the DB2 Connect Server

To access a remote server through NetBIOS, you must first have installed and configured communication software for both the client and DB2 Connect server workstations. See Software Requirements for the communication protocol requirements for your platform. See Possible Client-to-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.

The following steps are required to set up NetBIOS communications:

Identify and record parameter values.
Configure the server:
1. Configure the NetBIOS Interface.
2. 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 25. NetBIOS Values Required at the DB2 Connect Server

Parameter Description Sample Value Your Value
Adapter number (adapter_number)
The local logical adapters that will be used for the NetBIOS connection.
The server uses adapter 0 if this parameter is not configured.
0
Workstation name (nname)
The NetBIOS name of the server workstation.
nname is a name, chosen by the user, which must be unique among all NetBIOS server nodes in the network.
For more information on workstation names, see Workstation Names (nname)
server1

Parameter	Description	Sample Value	Your Value
Adapter number (`adapter_number`)	The local logical adapters that will be used for the NetBIOS connection. The server uses adapter `0` if this parameter is not configured.	`0`
Workstation name (`nname`)	The NetBIOS name of the server workstation. `nname` is a name, chosen by the user, which must be unique among all NetBIOS server nodes in the network. For more information on workstation names, see Workstation Names (nname)	`server1`

Step 2. Configure the DB2 Connect 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. Configure the NetBIOS Interface

This section describes how to configure the NetBIOS interface on your OS/2 or Windows NT DB2 Connect server.

For OS/2:
If the db2nbadapters parameter is not set, the default adapter will be 0. If you want to use additional server adapters, or you need to specify a server adapter other than 0, set the db2nbadapters parameter to the number you want to use.
For Windows NT:
In order for a client to connect to a Windows NT server, the network route of the adapter number used must be Nbf for native NetBIOS operation. If the db2nbadapters parameter is not set, the default local adapter will be 0. If you want to use additional server adapters, or you need to specify a server adapter other than 0, set the db2nbadapters parameter to the number that you want to use.

DB2 uses registry values to control its use of the NetBIOS resources on the server. Use the db2nbadapters registry parameter when you want to specify a value other than the default Logical adapter number 0.

For the DB2 server, set the db2nbadapters parameter by entering the db2set db2nbadapters=adapter_number command.

For the Administration Server, set the db2nbadapters parameter by entering the db2set db2nbadapters=adapter_number -i DB2DAS00 command.

For more information, see Chapter 41. Controlling Your DB2 Environment.

To view or modify the NetBIOS interface configuration, which maps network routes to adapter numbers, do the following:

For OS/2:
1. Double-click on the MPTS icon.
2. Click on the Configure push button.
3. Select the LAN adapters and protocols radio button and click on the Configure push button.
4. Record the Logical adapter number associated with the IBM OS/2 NETBIOS entry in the Current Configuration window.
5. If you want to change the logical adapter number associated with NetBIOS, select the IBM OS/2 NetBIOS entry from the Current Configuration window and click on the Change number push button.
6. Select a logical adapter number and click on the Change push button.
7. Record the new logical adapter number associated with the IBM OS/2 NETBIOS entry in the Current Configuration window on your worksheet.
8. Click on OK.
9. Click on the Close push button.
10. Click on the Exit push button.
11. Ensure that the Update CONFIG.SYS check box is selected and click on the Exit push button.
12. Click on the Exit push button.
13. The Network Settings Change pop-up box opens. You must shutdown and reboot your system for these changes to take effect. Select the Yes push button to shutdown and reboot your system or select the No push button to shutdown and reboot your system at a later time.

For Windows NT:

Click on Start and select Settings->Control Panel.
Double-click on the Network icon and select the Services tab.
Select the NetBIOS Interface icon from the Network Services window and click on the Properties push button.
Scroll through the network routes until you find the Logical adapter number associated with Nbf and record it on your worksheet. If this adapter number is associated with Nbf, and you do not want to change it, go to Step 7.
To change the logical adapter number associated with Nbf, select the associated Lana Number, and click on the Edit push button. Enter the new adapter number 0 (or the value that you set for db2nbadapters).
Record the new adapter number associated with Nbf on your worksheet.
Click on OK.
Click on the Close push button.
The Network Settings Change pop-up box opens. You must shutdown and reboot your system for these changes to take effect. Select the Yes push button to shutdown and reboot your system or select the No push button to shutdown and reboot your system at a later time.

Each adapter number must be uniquely associated with a network route. Windows NT has a built in checking facility that will not allow you to specify the same adapter number for different network routes. If a Network route already exists that is using the adapter number 0, assign a different number to that route. (The valid range for adapter numbers is 0 to 255.) This will allow you to select 0 as the adapter number that corresponds to Nbf. Approve the changes by clicking on OK.

B. Update the Database Manager Configuration File

You must update the database manager configuration file with the server's Workstation name (nname) parameter.

To update the database manager configuration file, perform the following steps:

Log on to the system with a user account that belongs to the local Administrators group on each machine in your partitioned database system.

If you have trouble logging on to the system, see Logging on to the System.
Update the database manager configuration file with the server's Workstation name (nname) parameter using the following commands in the command line processor:
```
   update database manager configuration using nname nname
   db2stop
   db2start
```
For example, if the server's workstation name (nname) is server1, use:
```
   update database manager configuration using nname server1
   db2stop
   db2start
```
If you are configuring the Administration Server for NetBIOS, you must update the admin server configuration file. Use the following command:
```
   update admin configuration using nname server1
   db2admin stop
   db2admin start
```

Now that you have configured the server, you are ready to install a DB2 client. Go to Chapter 27. Installing DB2 Clients for more information.

If you are configuring a DB2 Connect for OS/2 server, you are now finished the configuration and are ready to install a DB2 client. Go to Chapter 27. Installing DB2 Clients for more information.

Autostarting DB2 with NetBIOS (for Windows NT only)

If your NetBIOS protocol was configured when you installed on the instance-owning machine, the setup program automatically created a dependency on NetBIOS for the Administration Server and the default instance (DB2). If you create additional DB2 instances, you will need to manually create a dependency on NetBIOS for each new instance.

You can create this dependency with the db2depnb command as follows:

Go to the x:\sqllib\misc directory, where x: is the drive on which DB2 was installed
Enter the db2depnb command as follows:
```
db2depnb instance_name
```

This records a dependency on the startup order which causes NetBIOS to start before any DB2 instances start.

If you remove the NetBIOS protocol from your network, you must remove the dependencies that were created during installation, and any dependencies that you created for additional instances. Failure to remove these dependencies may cause problems when running DB2 after the NetBIOS protocol has been removed from the network.
To remove a dependency, enter the db2depnb command as follows:
db2depnb instance_name /r

where instance_name is the name of the instance for which you removed a dependency.

Now that you have configured the server, you are ready to install a DB2 client. Go to Chapter 27. 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 ]