Administration Guide
Figure 121 shows a sample configuration of a database
network with two DCE cells.
/.../CELL_TORONTO and
/.../CELL_VANCOUVER are the names of the
cells. (Each of these cells contains a directory called
/.:/subsys/database/ and while not illustrated in
diagram, is used in other examples.)
Figure 121. Configuration of A Network Database
To allow the clients in the TORONTO cell to access all the databases in both
cells, values must be specified in the database manager configuration
parameters and the following objects must be created:
- A database object for each database.
- A database locator object for the two database servers for DB2 for AIX and
DB2 for OS/2.
- A single routing information object that is known to all clients.
The attributes specify which DB2 Connect node to use for the MVSDB and VMDB
databases.
The following provide examples of how a client connects to a
database:
These examples include the database manager configuration parameters that
must be specified.
This section describes several examples of how clients
connect to databases in the same cell.
- Client_1 connects to AIXDB2. The database shares the same
directory path name as the client.
The database administrator needs to:
- Specify the directory path name value in the configuration parameter
dir_path_name (or the DB2DIRPATHNAME registry value).
- Specify the directory services type value to be DCE in the configuration
parameter dir_type.
- Specify the communication protocol in the configuration parameter
dft_client_comm (or the DB2CLIENTCOMM registry value).
The local system database directory does not contain AIXDB2, so the DCE
directory is searched using the fully-qualified name. The name is
created by concatenating the value for the configuration parameter
dir_path_name (or the DB2DIRPATHNAME registry value) with
AIXDB2.
The sequence of events is:
- Client_1 obtains the database object for AIXDB2 using the DCE name of
the database
/.../CELL_TORONTO/subsys/database/AIXDB2.
- From this object, Client_1 knows that AIXDB2 uses the DB protocol
DB2RA, which is the same protocol that Client_1 uses.
- The DB protocols match, so Client_1 reads the DBMS locator object for
AIX_INST, retrieves the communications protocol attribute value that matches
the one it uses, and uses the information to start a conversation with that
DBMS instance.
- Client_3 connects to MVSDB. The database shares the same
directory path name as the client and uses a different database protocol from
the client.
The database administrator needs to:
- Specify the directory path name value in the configuration parameter
dir_path_name (or the DB2DIRPATHNAME registry value).
- Specify the directory services type value to be DCE in the configuration
parameter dir_type.
- Specify the communication protocol in the configuration parameter
dft_client_comm (or the DB2CLIENTCOMM registry value).
- Specify the DCE name of the default routing information object in the
configuration parameter route_obj_name (or the DB2ROUTE registry
value).
The sequence of events is:
- Client_3 obtains the database object for MVSDB using the DCE name of
the database
/.../CELL_TORONTO/subsys/database/MVSDB.
- From this object, Client_3 finds that MVSDB only uses the DB protocol
DRDA, which is not the protocol that Client_3 uses.
- Client_3 then obtains the routing information object using the name
defined in the route_obj_name configuration parameter or the
DB2ROUTE registry value. The client finds the target database
information for MVSDB.
- Client_3 reads the database locator object associated with the MVSDB
target database information, retrieves the communication protocol, and sends
an SQL CONNECT request to the router.
- The router then sets up an APPC connection with MVSDB.
This section describes an example of how a client connects to a database in a
different cell when the database protocols are different.
- Client_3 has previously been configured to use the following:
- In order for Client_3 to connect to VMDB, the database administrator
needs to:
The sequence of events is:
- Client_3 finds the fully qualified DCE name of VANVMDB in its system
database directory.
- Client_3 obtains the database object for VMDB using the DCE name of the
database
/.../CELL_VANCOUVER/subsys/database/VMDB.
- From this object, Client_3 finds that VMDB only uses the DB protocol
DRDA, which is not the protocol that Client_3 uses.
- Client_3 then obtains the routing information object using the name
defined in the route_obj_name configuration parameter or the
DB2ROUTE registry value. The client finds the target database
information for VMDB.
- Client_3 reads the database locator object associated with the VMDB
target database information and retrieves the communication protocol and sends
an SQL CONNECT request to the router.
- The router then sets up an APPC connection with VMDB.
[ Top of Page | Previous Page | Next Page ]