OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components

toofewservers and returns its associated value.

dcecp> dts show -counters

{creationtime 1994-09-16-07:50:13.067-04:00I-----}

{nointersections 0}

{diffepochs 0}

{toofewservers 1}

{providertimeouts 82}

{badprotocols 0}

{badtimerep 0}

{noglobals 81}

{noresponses 0}

{abrupts 0}

{epochchanges 0}

{syserrors 0}

{syncs 1574}

{updates 0}

{enables 1}

{disables 0}

{nomemories 0}

{providerfailures 0}

{badlocalservers 0}

{badservers 0}

dcecp> attrlist getvalues $_r -type toofewservers

dcecp>

2.6.8 DCE Servers to Use (_s(xxx))

The _s( xxx) variables hold the names of the DCE servers to use for the next DCE

operation. The DCE control program provides four of these variables. Because the

variables are not set by dcecp, users must set these variables if they want to use them.

The variables are as follows:

_s(sec) This variable holds the name of the security server you want to use for

the next registry operation. If you set this to specify a read-only replica

and the operation (such as principal create) requires a master replica,

dcecp ignores the variable and tries to bind to the master registry.

Registry operations that use the _s(sec) variable include principal,

group, organization, registry, account, and xattrschema.

DCE control program operations use the _s(sec) variable in conjunction

with the _b(sec) variable, which holds the name of the most recent

registry used. A registry operation uses the following order to select a

security server:

1. Use the server passed as a name argument to the registry

operation.

2− 12 Tandem Computers Incorporated 124243