Installation and Configuration Supplement

Configuring NetBIOS on the Client

This section assumes that NetBIOS is functional on the client and 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.

To set up a client to use NetBIOS communications, perform the following steps:

Step  1.	Identify and record parameter values.
Step  2.	Configure the client: Record the logical adapter number used for the NetBIOS connection. Update the database manager configuration file. Catalog the NetBIOS node. Catalog the database.
Step  3.	Test the connection between the client and server.

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 12. NetBIOS Values Required at the Client

Parameter	Description	Sample Value	Your Value
Logical adapter number (adapter_number)	The local logical adapter that will be used for the NetBIOS connection.	0
Workstation name (nname) - on the client	The NetBIOS name of the client workstation. nname is chosen by the user and must be unique among all NetBIOS nodes in the network.	client1
Workstation name (nname) - on the server	The NetBIOS name of the server workstation. Locate this parameter in the database manager configuration file on the server.	server1
Node name (node_name)	A local alias, or nickname, that describes the node to which you are trying to connect. You can choose any name you want, however, all node name values within your local node directory must be unique.	db2node

Step 2. Configure the Client

The following steps configure the client to communicate with the server using TCP/IP. Replace the sample values with your worksheet values.

A. Record the Logical Adapter Number of the Local Logical Adapter Used for the NetBIOS Connection

To view and record the logical adapter number (adapter_number) used for the NetBIOS connection, perform the following steps:

• For OS/2:
  1. Double-click on the OS/2 System icon.
  2. Double-click on the System Setup icon.
  3. Double-click on the MPTS Network Adapters and Protocol Services icon.
  4. Click on the Configure push button.
  5. Select the LAN adapters and protocols radio button and click on the Configure push button.
  6. Record the Logical adapter number associated with the IBM OS/2 NETBIOS entry in the Current Configuration window.
  7. Click Cancel.
  8. Click Close.
  9. Click Exit.
• For Windows 32-bit operating systems:
  1. From a command prompt, enter the regedit command to start the Registry Editor
  2. Locate the NetBIOS adapter assignments by expanding the HKEY_LOCAL_MACHINE folder and locating the Software/Microsoft/Rpc/NetBIOS folder.
  3. Double-click on the entry that begins with ncacn_nb_nx, where x can be 0, 1, 2.. (normally you want to select the nb0 adapter), to see that adapter number that is associated with the NetBIOS connection. Record this setting from the Value field in the pop-up window.

B. Update the Database Manager Configuration File

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

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

Step  1.	Log on to the system as a user with System Administrative (SYSADM) authority. For more information, see Working with the System Administrative Group.
Step  2.	Update the database manager configuration file with the client's Workstation name (nname) parameter using the following commands in the command line processor: update database manager configuration using nname nname terminate For example, if the client's workstation name (nname) is client1, use: update database manager configuration using nname client1 terminate

C. Catalog the NetBIOS Node

You must add an entry to the client's node directory to describe the remote node. This entry specifies the chosen alias (node_name), the remote server's workstation name (nname), and the Logical adapter number (adapter_number) that the client will use to access the remote DB2 server.

To catalog the NetBIOS node, perform the following steps:

Step  1.

Log on to the system with a valid DB2 user ID. For more information, see Appendix F, Naming Rules. If you are adding a database to a system that has a DB2 server or DB2 Connect server product installed, log on to this system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority on the instance. For more information, see Working with the System Administrative Group. This restriction is controlled by the catalog_noauth database manager configuration parameter. For more information, refer to the Administration Guide.

Step  2.

Catalog the node by entering the following commands in the command line processor: catalog netbios node node_name remote nname adapter adapter_number terminate For example, to catalog a remote database server server1 on the node called db2node, using the logical adapter number 0, use: catalog netbios node db2node remote server1 adapter 0 terminate

If you need to change values that were set with the catalog node command, perform the following steps: Step  1. Run the uncatalog node command in the command line processor as follows: db2 uncatalog node node_name Step  2. Recatalog the node with the values that you want to use.

D. Catalog the Database

Before a client application can access a remote database, the database must be cataloged on the server node and on any client nodes that will connect to it. By default, when you create a database, it is automatically cataloged on the server with the database alias (database_alias) the same as the database name (database_name). The information in the database directory, along with the information in the node directory, is used on the client to establish a connection to the remote database.

To catalog a database on the client, perform the following steps:

Step  1.	Log on to the system with a valid DB2 user ID. For more information, see Appendix F, Naming Rules. If you are adding a database to a system that has a DB2 server or DB2 Connect server product installed, log on to this system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority on the instance. For more information, see Working with the System Administrative Group. This restriction is controlled by the catalog_noauth database manager configuration parameter. For more information, refer to the Administration Guide.
Step  2.	Fill in the Your Value column in the following worksheet. Table 13. Worksheet: Parameter Values for Cataloging Databases Parameter Description Sample Value Your Value Database name (database_name) The database alias (database_alias) of the remote database. When you create a database, it is automatically cataloged on the server with the database alias (database_alias) the same as the database name (database_name), unless specified otherwise. sample   Database alias (database_alias) An arbitrary local nickname for the remote database, on the client. If you do not provide one, the default is the same as the database name (database_name). The database alias the name that you use when connecting to a database from a client. tor1   Authentication (auth_value) The value of the authentication required by your enterprise. Please refer to the DB2 Connect User's Guide for more information on this parameter. DCS This means that the userid and password supplied are validated at the host or AS/400 only.   Node name (node_name) The name of the node directory entry that describes where the database resides. Use the same value for node name (node_name) that you used to catalog the node in the previous step. db2node
Step  3.	Catalog the database by entering the following commands: db2 catalog database database_name as database_alias at node node_name db2 terminate For example, to catalog a remote database called sample so that it has the alias tor1, on the node db2node, enter the following commands: db2 catalog database sample as tor1 at node db2node db2 terminate If you need to change values that were set with the catalog database command, perform the following steps: Step  a. Run the uncatalog database command as follows: db2 uncatalog database database_alias Step  b. Recatalog the database with the value that you want to use.

Step 3. Test the Client-to-Server Connection

After configuring the client for communications, you will need to connect to a remote database to test the connection.

Step  1.	Start the database manager by entering the db2start command on the server (if it was not automatically started at boot time).
Step  2.	If you are using a UNIX client, run the start-up script as follows: . INSTHOME/sqllib/db2profile (for Bash, Bourne or Korn shell) source INSTHOME/sqllib/db2cshrc (for C shell) where INSTHOME represents the home directory of the instance.
Step  3.	Enter the following command on the client to connect the client to the remote database: db2 connect to database_alias user userid using password

The values for userid and password must be valid for the system on which they are authenticated. By default, authentication takes place on the server for a DB2 server and on the host or AS/400 machine for a DB2 Connect server.

If the connection is successful, you will get a message showing the name of the database to which you have connected. You are now able to retrieve data from that database. For example, to retrieve a list of all the table names listed in the system catalog table, enter the following SQL command in the Command Center or CLP:

     "select tabname from syscat.tables"

When you are finished using the database connection, enter the command reset command to end the database connection.

The values for userid and password must be valid for the system on which they are authenticated. By default, authentication takes place on the server for a DB2 server and on the host or AS/400 machine for a DB2 Connect server.

If the connection is successful, you will get a message showing the name of the database to which you have connected. You are now able to retrieve data from that database. For example, to retrieve a list of all the table names listed in the system catalog table, enter the following SQL command in the Command Center or command line processor:

   "select tabname from syscat.tables"

When you are finished using the database connection, enter the db2 connect reset command to end the database connection.

Troubleshooting the Client-to-Server Connection

If the connection fails, check the following items:

At the server:

__  1.	The db2comm registry value includes the value netbios. Check the settings for the db2comm registry value by entering the db2set DB2COMM command. For more information, refer to the Administration Guide.
__  2.	The logical adapter number is equal to 0 (or the DB2NBADAPTERS registry value was updated to override the default value).
__  3.	The server's workstation name (nname) parameter was updated correctly in the database manager configuration file (or the admin configuration file, if you are setting up the Administration Server).
__  4.	The network route associated with the logical adapter number is Nbf (for Windows NT and Windows 2000 servers only).
__  5.	The security service was started. Enter the net start db2ntsecserver command (for Windows NT and Windows 2000 servers only).
__  6.	The database was created and cataloged properly.
__  7.	The database manager was stopped and started again (enter the db2stop and db2start commands on the server).

If there are problems starting a protocol's connection managers, a warning message appears and the error messages are logged in the db2diag.log file located in the INSTHOME/sqllib/db2dump directory for UNIX platforms or in the x:\sqllib\db2dump directory for non-UNIX platforms. For more information on the db2diag.log file, refer to the Troubleshooting Guide.

At the client:

__  1.	The client's workstation name (nname) parameter was updated correctly in the database manager configuration file.
__  2.	The node was cataloged with the correct server's workstation name (nname) and local logical adapter number (adapter_number).
__  3.	The node name (node_name) that was specified in the database directory points to the correct entry in the node directory.
__  4.	The database was cataloged properly, using the server's database alias (the database_alias that was cataloged when the database was created on the server), as the database name (database_name) on the client.

If the connection still fails after you verify these items, refer to the Troubleshooting Guide.