VMS Help DCE, dce_tools_intro, dced  *Conan The Librarian (sorry for the slow response - running on an old VAX)

  NAME
    dced - DCE Host daemon

  SYNOPSIS

    dced [-ifh] [-w route] [-b|-p|-s] [-e|prot_seq...]

  OPTIONS

   -h        Prints the dced usage and exits.

   -i        Initializes the dced databases and ACLs and exits. If the
             databases exist, this option displays an error.  See the
             list of databases in the FILES section.

   -b        Starts dced in bootstrap mode with the endpoint mapper
             service and ACLs.  This mode means it may need to wait
             for other daemons such as secd and cdsd before it can
             perform its own initialization.

   -c        Starts dced so it does not require DCE privacy encryption
             for remote key table management.  The default is to use
             DCE privacy encryption.

   -e        Starts dced without the endpoint mapper service.  No
             protocol sequences are valid for this option.

   -f        Starts the dced process in the foreground. The default is
             for dced to run in the background.

   -p        Purges the existing machine context and removes the bindings
             file before starting.

   -s        Starts dced without the security validation service.

   -w        Sets the routing for serviceability.

  ARGUMENTS

             Establishes the serviceability routing for dced's messages.

             Starts dced by using the specified RPC protocol sequence
             string or strings. Possible values include ncadg_ip_udp
             (for a datagram protocol) and ncacn_ip_tcp (for a
             connection-based protocol). A complete list of the protocol
             sequences recognized can be found in dce/ep.idl.

  DESCRIPTION

  The DCE Host daemon is a process that provides services for the local
  host, and is also the server used by remote applications to access
  these host services.  The DCE Host daemon services include the
  following:

  Endpoint Mapper
             The endpoint mapper service maintains a database called the
             local endpoint map which allows DCE clients to find servers,
             individual services provided by servers, and objects managed
             by services on the host. The endpoint mapper service maps
             interfaces, object UUIDs, and protocol sequence
             registrations to server ports (endpoints). Servers register
             their bindings with the local endpoint mapper, and the end-
             point mapper service on each host uses the local endpoint
             map to locate a compatible server for clients that do not
             already know the endpoint of a compatible server.

  Host Data Management
             The host data management service maintains local files of
             host data that include (among others) the host_name,
             cell_name, cell_aliases, and a post_processors file. The
             post_processors file contains program names matched with
             the other host data items (UUIDs). The dced runs the program
             if the corresponding host data item is changed.  There may
             also be host-specific data files.

  Server Management
             The server management service maintains data that describes
             the startup configuration (srvrconf) and execution state
             (srvrexec) for each server. It also has the functionality
             to start or stop particular servers, and enable or disable
             specific services of servers.

  Security Validation
             The security validation service acts as the client side of
             the security server by assuring applications that the DCE
             Security daemon (secd) that the host is using is legitimate.
             In addition, this service logs into the local machine when
             dced is invoked and automatically updates the local machine
             principal's keys.

  Key Table Management
             The key table management service allows for remote
             maintenance of server's key tables (keytab files).

  The DCE Host daemon must be running before any other DCE-based servers
  are started. Each DCE host must run only a single dced, and it must run
  with privileges since it typically listens on privileged or reserved
  network ports.  Typically, dced starts each time a host boots. (A file
  called SYS$MANAGER:DCE$RPC_STARTUP.COM is responsible for configuration
  issues such as deleting the endpoint map database and starting dced.)

  By default, the DCE Host daemon listens on one well-known port for each
  RPC protocol sequence (that is, each combination of an RPC protocol and
  a transport protocol) supported by the host on which it is running.  A
  prot_seq argument lets you limit the protocol sequences on which dced
  listens.

  FILES

  dce$local:[var.dced]Ep.db            dce$local:[var.dced]cell_aliases
  dce$local:[var.dced]Hostdata.db      dce$local:[var.dced]cell_name
  dce$local:[var.dced]Srvrconf.db      dce$local:[var.dced]host_name
  dce$local:[var.dced]Srvrexec.db      dce$local:[var.dced]Acl.db
  dce$local:[var.dced]Keytab.db        dce$local:[krb5]v5srvtab
  dce$local:[var.dced]Xattrschema.db   dce$local:[000000]dce_cf.db
  dce$local:[var.dced]post_processors

  RELATED INFORMATION
      COMMANDS: hostdata, endpoint, server, secval, keytab, attribute

      LIBRARY CALLS: dce_server*, dced_*, rpc_mgmt_ep*

      BOOKS: OSF DCE Application Development Guide.