Interpretation of 'dsom' messages

The messages generated by the dsom utility have a one-to-one mapping on the DSOM error codes. Knowing this mapping will aid in a better understanding of the dsom return messages. The following six messages are mapped onto the DSOM error code of 0 (success):

• dsom' cmd
  Message
  start
  **Started server process**
  restart
  **Restarted server process**
  list
  **Server process currently running**
  stop
  **Stopped server process**
  disable
  **Successfully disabled server**
  enable
  **Successfully enabled server**

  The messages generated by the dsom utility commands are mapped onto DSOM error codes, as follows:

  ┌──────────────────────────────┬─────────────────────────────────────────────┐│DSOM ERROR CODE               │MESSAGE                                      │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_ServerNotFound      │**Server process not running**               │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_NotProcessOwner     │**Cannot stop server; Not process owner**    │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_NoSocketsClass      │**Cannot find Sockets class**                │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_NoRemoteComm        │**Not enabled for Workgroup**                │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_CommTimeOut         │**Client timed out**                         │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_SendError           │**Send Error**                               │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_SocketSend          │**Send Error**                               │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_ServerInactive      │**Server activation pending**                │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_NoSOMDInit          │**Unable to create global LocSerObject**     │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_UnknownError        │**Command not supported by daemon*           │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_ServerDisabled      │**Server process is currently disabled**     │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_CouldNotStartProcess│**Server process cannot be started**         │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │SOMDERROR_ServerToBeDeleted   │**Current server process marked for deletion;│
  │                              │try again**                                  │
  ├──────────────────────────────┼─────────────────────────────────────────────┤
  │Any other error               │**Request unsuccessful; Unknown error**      │
  └──────────────────────────────┴─────────────────────────────────────────────┘
  

  In addition, if the impl_alias specified with any dsom utility command is not present in the Implementation Repository, DSOM will generate the message: **Server alias not found in Implementation Repository**.

  Programmatic interface to manage server processes

  Server processes can also be managed by using the programmatic interface provided by the SOMDServerMgr class. For descriptions of the SOMDServerMgr class and its corresponding methods, see the DSOM section of the SOMobjects Developer Toolkit Programmers Reference Manual.

  ---

  [Back: The 'dsom' server manager utility]
  [Next: Verifying the DSOM environment with 'somdchk']