The tasks that must be performed to setup and use DCE Directory Services are
listed below. The following sections describe the details of each
- "DCE Administrator Tasks"
The DCE administrator must update the DCE directory so that the new
database resource information can be added.
- "Database Administrator Tasks"
The database administrator must update the DCE directory and supply
information for DB2 installation and configuration.
- "Database User Tasks"
The database user must log in to DCE and know the target database
In addition, the network administrator sets up the network access for each
user node. Refer to the network documentation for the details.
The DCE administrator must do the following tasks before
the directory objects can be created or read:
- Assign the directory subtree for DB2, for example
- Grant the privileges to the database administrator to create directory
- Grant the privileges to the database users to read the directory objects
- Add the information for the new DCE directory object attributes to the
DCE attribute table.
Edit the CDS attributes file (on UNIX platforms
/etc/dce/cds_attributes; on OS/2
X:\opt\dcelocal\etc\cds_attr, where "X" is the appropriate
drive) and append the following:
18.104.22.168.2.4.30 DB_Comment char
22.214.171.124.2.4.31 DB_Communication_Protocol char
126.96.36.199.2.4.32 DB_Database_Protocol char
188.8.131.52.2.4.33 DB_Database_Locator_Name char
184.108.40.206.2.4.34 DB_Native_Database_Name char
220.127.116.11.2.4.35 DB_Object_Type char
18.104.22.168.2.4.36 DB_Product_Name char
22.214.171.124.2.4.37 DB_Product_Release char
126.96.36.199.2.4.38 DB_Target_Database_Info char
188.8.131.52.2.4.39 DB_Authentication char
184.108.40.206.2.4.63 DB_Principal char
- Ensure DCE is running when users need access to the databases using DCE
For more information, refer to the DCE documentation for the platform you
The database administrator must do the following
- Obtain the directory subtree for the database resources from the DCE
administrator. For example, /.:/subsys/database
- During installation of the DB2 database manager, ask the DCE administrator
to add the new DCE directory object attributes required by DB2.
- Assign a unique name for each DBMS instance in the DCE directory
subtree. For example,
- For each DBMS instance specify the database manager configuration
parameters for DCE.
Some of the configuration parameters can be temporarily overridden by
registry values set by the client. Refer to "Configuration Parameters and Registry Variables" for more information.
- Assign a unique name for each database in the DCE directory
subtree. Specify the name in the dir_obj_name parameter in
the database configuration file.
- Create the objects for DCE Directory Services using the DCE
cdscp commands to create and display objects. The objects
are created separately from the database manager installation process and the
database manager instance start process.
Three types of objects exist.
- A database object is required for each target database.
- A database locator object is required for each DB2 Connect instance and
each DBMS instance (without DB2 Connect) which is associated with more than
- Routing information objects are required to access a host database.
- Depending on each environment, the database administrator must
- How to group the clients into logical groups considering what databases
they access, and what communications protocols they use.
- How many routing information objects are required.
- Which target databases should be recorded in each routing information
- Which routing information objects should be known to which group of
Refer to "Creating Directory Objects" for details about the objects.
The database user must do the following tasks:
- Obtain the name of the database from the database administrator.
This name can be a simple one-part name, or a fully-qualified DCE name.
- If needed, specify the values required for DCE Directory Services in the
registry values. Registry values set by the client can temporarily
override the configuration parameters.
- If host database access is required, obtain the fully-qualified DCE name
of the routing information object from the database administrator. If
this name is not specified in the route_obj_name, or it is a
different name, specify this name in the DB2ROUTE registry value before trying
to connect to the host database.
- If your preferred communication protocol is not specified in
dft_client_comm, or it is a different protocol, specify the
communication protocol for the client in the DB2CLIENTCOMM registry
value. Here are some UNIX examples:
Some OS/2 examples are:
Some Windows NT and Windows 95 examples are:
If more than one communication protocol exists, the first one specified is
- If any of the databases has a DCE name that is not in the directory path
defined in the dir_path_name configuration parameter or the
DB2DIRPATHNAME registry value, then explicitly catalog the database with the
CATALOG GLOBAL DATABASE command. Refer to "CATALOG GLOBAL DATABASE Command" for more information.
- Log in to DCE before connecting to the target database or attaching to the
database instance. Refer to the OSF DCE Administration Guide for more information about the login command.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]