PreviousNext

Temporarily Reconfiguring DTS

From time to time, a situation or problem may arise in your network that requires you to temporarily reconfigure DTS on one or more nodes. Perhaps a node in the LAN is having problems and you need to have another node take over the clerk or server role of the problem node. Rather than adding an unnecessary server or clerk to the network, you can convert the clerk or server so that it plays the needed role.

If you convert a clerk or server, the change is only temporary. When DCE is stopped and restarted on a node, the node will revert to its initial DTS configuration. A node that was initially configured as a DTS server will become a server; a node that was initially configured as a DTS clerk, will become a clerk. In order to permanently change the DTS configuration on a node, you must run the dce_config script as discussed in Reconfiguring DTS on Nodes.

To temporarily convert a clerk to a server, or vice versa, perform these steps:

1. Stop the clerk or server process that is currently executing on the node by using the dcecp dts stop command:

dcecp> dts stop
dcecp>

After you stop the clerk or server, quit dcecp.

2. Restart the DTS daemon on the node as a clerk or server by executing the dtsd command with the appropriate option (the -c option for a clerk or the -s option for a server). For example, to create a local server, you enter the following command:

> dtsd -s

The example command creates a local server that is a backup courier (the server's courierrole attribute value is set to backup by default). If desired, you can designate another courier role for the server in the dtsd command line by using the command's -k option. Other than a backup courier, the local server created in the example can be a courier (courier) or cannot have any courier role (noncourier).

In the following example, the local server is given the role of a courier:

> dtsd -s -k courier

To create a global server, you enter the dtsd command with the -g option:

> dtsd -s -g

Note: If you are reconfiguring a node that previously ran a DTS clerk so that it runs a DTS server, you need to perform extra steps. You must create a principal account for the new server in the Security Service registry, and you must add the server's name to the existing DTS server group (dts-entity). Otherwise, DTS clerks will not be able to find the newly created server. For instructions on creating a principal account, see Creating and Maintaining Accounts of this guide. For instructions on adding a principal name to a group, refer to Creating and Maintaining Principals, Groups, and Organizations.

3. Set any clerk or server attribute values as needed by using the DCE control program's dts modify command. The following topic provides instructions for modifying DTS clerk and server attributes.