If all servers ran as persistent processes, dced could maintain data about each server in a single (albeit complex) data structure. However, due to the fact that some servers may run on demand, it is a more flexible design to have two sets of data: one that describes the default configuration to start the server, and one that describes the executing (running) server. Earlier in this topic when we described dced service naming, we defined srvrconf and srvrexec objects to name the two portions of the server management service.
The following table lists the routines that applications can use to control servers. It also shows the valid object names to use when establishing a dced binding prior to using the routine.
API Routines for Remote Server Management
| API Routine | Service Name for Binding |
| dced_server_create( ) | srvrconf |
| dced_server_start( ) | srvrconf |
| dced_server_disable_if( ) | srvrexec |
| dced_server_enable_if(~) | srvrexec |
| dced_server_stop( ) | srvrexec |
| dced_object_read( ) | srvrexec or srvrconf |
| dced_object_read_all( ) | srvrexec or srvrconf |
| dced_server_modify_attributes( ) | srvrconf |
| dced_server_delete( ) | srvrconf |