Quick Beginnings for DB2 Extended Enterprise Edition for UNIX
This section assumes that IPX/SPX is functional on 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.
A client can access a DB2 Extended Enterprise Edition server via Direct
Addressing only. For a description of Direct Addressing, see "Configuring IPX/SPX on the Server".
The following steps are required to set up a DB2 client to use IPX/SPX
communications:
- Identify and record parameter values.
- Configure the client:
- Catalog the IPX/SPX node.
- Catalog the database.
- Test the connection between the client and server.
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 16. IPX/SPX Values Required at the Client
| Parameter
| Description
| Sample Value
| Your Value
|
| File server name (FILESERVER)
|
- Direct Addressing
- A * value indicates that you are using Direct Addressing.
Locate this parameter in the database manager configuration file on the
server.
|
- Direct Addressing
- *
|
|
| DB2 server object name (OBJECTNAME)
|
- Direct Addressing
- The server's IPX/SPX internetwork address of the form:
netid
(8 byte).nodeid (12 byte).
socket # (4 byte)
To resolve this parameter, issue the db2ipxad command at the
server. See "A. Catalog the IPX/SPX Node" for more information.
Locate this parameter in the database manager configuration file on the
server.
|
- Direct Addressing
- 09212700.400011527745.879E
|
|
| Node name (node_name)
|
A local alias, or nickname, that describes the node where the database
resides. You can choose any name you want, however, all node name
values within your local node directory must be unique.
| db2node
|
|
The following steps describe how to configure this protocol
on the client. Replace the sample values with your worksheet
values.
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 file server
name (FILESERVER), and the DB2 server object name
(OBJECTNAME) that the client will use to access the remote DB2
server.
To catalog the IPX/SPX node, perform the following steps:
- Log on to the system as a user with System Administrative (SYSADM) or
System Controller (SYSCTRL) authority.
- If you are using a UNIX client, set up the instance environment and invoke
the DB2 command line processor as follows:
- 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.
- Start the DB2 command line processor by issuing the db2
command.
- Catalog the node by issuing the following commands in the command line
processor:
catalog ipxspx node node_name remote FILESERVER server OBJECTNAME
terminate
- Direct Addressing Example
-
You must assign a * to the FILESERVER parameter and
specify the server's IPX/SPX internetwork address value as the
OBJECTNAME parameter on the client.
To determine the value for the OBJECTNAME parameter, issue the
db2ipxad command on the server. (This command is located in
the sqllib/misc/ directory.)
Make note of the output that is generated, and use that value in place of
the sample value (09212700.400011527745.879E) in the
example that follows.
To catalog a remote node called db2node, using the IPX/SPX
internetwork address 09212700.400011527745.879E as the
OBJECTNAME, use:
catalog ipxspx node db2node remote * server 09212700.400011527745.879E
terminate
|
If you need to change values that were set with the catalog node
command, first run the uncatalog node command in the command line
processor as follows:
uncatalog node node_name
Recatalog the node with the value that you want to use.
|
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. 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.
- Log on to the system as a user with System Administrative (SYSADM) or
System Controller (SYSCTRL) authority.
- Fill in the Your Value column in the following
worksheet.
Table 17. 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 name (database_alias) the same as
the database name (database_name).
| 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). This is the name that you use
when connecting to a database from a client.
| tor1
|
|
| 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
|
|
- If you are using a UNIX client, set up the instance environment and invoke
the DB2 command line processor as follows:
- 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.
- Start the DB2 command line processor by issuing the db2
command.
- Catalog the database by issuing the following commands in the command line
processor:
catalog database database_name as database_alias at node node_name
terminate
For example, to catalog a remote database called sample so that
it has the alias tor1, on the node db2node, use:
catalog database sample as tor1 at node db2node
terminate
|
If you need to change values that were set with the catalog
database command, first run the uncatalog
database command in the command line processor as
follows:
uncatalog database database_alias
Recatalog the database with the value that you want to use.
|
When the configuration of the server and client is complete,
use the following steps to verify that you can access data from a remote
database:
|
You will need to connect to a remote database to test the
connection. If you do not have a database on the server, create the
sample database on the server to test the connection. See "Creating the Sample Database" for more information.
|
- Start the database manager by issuing the db2start command on
the server (if it was not automatically started at boot time).
- Enter the following command in the client's Command Center or command
line processor to connect the client to the remote database:
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. If the database manager is configured for
CLIENT authentication, the userid and password must be valid
on the client.
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 connect
reset command to end the database connection.
If the connection fails, check the following items:
At the server:
- The db2comm registry value includes the value
ipxspx. db2comm can be set in the
db2profile or the db2cshrc file.
- The FILESERVER, OBJECTNAME, and IPX_SOCKET
parameters were updated correctly in the database manager configuration
file.
- The database was created and cataloged properly.
- The database manager was stopped and started (enter the db2stop
and db2start commands on the server).
|
If there are problems starting a protocol's connection managers, a
warning message is displayed and the error messages are logged in the
db2diag.log file, located in the instance
directory.
Additionally, any failure encountered while executing the
db2start command is logged to a time-stamped file in the log
subdirectory within the instance directory. This file contains the
db2start results from each database partition server in the
instance.
If there is no error when the db2start command is run, these
files are removed.
Refer to the Troubleshooting Guide for information on the db2diag.log file.
|
At the client:
- Check that the node was cataloged with a value of * for
FILESERVER, and the correct IPX/SPX internetwork address value for
the OBJECTNAME parameter.
- The node name (node_name), specified in the database directory,
points to the correct entry in the node directory.
- The database was cataloged properly, using the server's
database alias (database_alias) that was cataloged when the database
was created on the server, as the database name (database_name) on
the client.
After you verify these items, refer to the Troubleshooting Guide if the connection still fails.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]
