Administration Guide

Configuration Parameters and Registry Variables

The following configuration parameters are used with DCE directories. An example of the values is shown. Refer to "Distributed Services" for details.

dir_obj_name is the database instance name which is concatenated with dir_path_name. If the instance name is used as the target of the ATTACH command, the name must be less than or equal to 8 characters and all upper case, for example:
```
   AIX_INST
```
dir_type identifies whether or not to use DCE directory services. To enable DCE directory services, this parameter must be set to:
```
   DCE
```
Note that dir_type is set to NONE and cannot be updated on database clients that do not support the use of DCE directory services.
dir_path_name is the directory path name provided by the DCE administrator, for example:
```
   /.:/subsys/database/
```
route_obj_name is an optional parameter that provides the name of the routing information object. The name can be fully-qualified, for example:
```
   /.:/subsys/database/ROUTE1
```
or a one-part name that will be concatenated with dir_path_name, for example:
```
   ROUTE1
```

dft_client_comm is an optional parameter that specifies the communications protocol used by the client, for example:

   TCPIP

This parameter can also specify more than one protocol, for example:

   TCPIP,APPC   (on UNIX-based platforms)
   TCPIP,APPC,IPXSPX,NETBIOS    (on OS/2 platforms)
   TCPIP,APPC,IPXSPX,NETBIOS,NPIPE    (on Windows NT or Windows 95 platforms)

dft_client_adpt is an optional parameter that specifies the default client adapter number for the NetBIOS protocol on OS/2, Windows NT, or Windows 95. The valid range of numbers is zero through fifteen (0 to 15). If this parameter contains a non-numeric value, then the value defaults to zero (0). If this parameter contains a value outside the range allowed, then the value defaults to zero (0).

For the following parameters, registry variables can override the parameter values.

Configuration Parameter: Registry Variable
dir_path_name: DB2DIRPATHNAME
route_obj_name: DB2ROUTE
dft_client_comm: DB2CLIENTCOMM
dft_client_adpt: DB2CLIENTADPT

The rules for setting these registry variables is the same as their corresponding configuration parameter. For example, like the dft_client_comm parameter, the DB2CLIENTCOMM is a character string that can have multiple values, each separated by a comma, for example:

   db2set DB2CLIENTCOMM=TCPIP,APPC

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]