Control message (SMObject/TCPIP/Control)

1. SM_control_reset_connection
   

   It requests a control server to send SIGUSR1 to the engine. The control server should immediately reply an acknowledgment to the client.

   Request:

   int32 OX_COMMAND

   int32 SM_control_reset_connection

   Result: none.
   

   All engines are encouraged to install the reset protocol, but when it is not implemented, no_ox_reset option should be included in the fourth argument (option list) of the mathcap (ref: oxpari).
   

   Note: Some old implementations of control servers and clients (before 2000) assume the result code of the following format. These obsolete implementations should be updated.
   

   int32 OX_DATA

   CMO_INT32 result

   
   

2. SM_control_kill
   

   It requests a control server to terminate the engine and the control server itself. All files and streams should be closed before the termination of servers.

   Request:

   int32 OX_COMMAND

   int32 SM_control_kill

   
   Result: none.

Example: (serial numbers are omitted.)

0  0 2 01 (OX_COMMAND) 
0  0 4 06 (SM_control_reset_connection)

OX_SYNC_BALL are exchanged on the data channel for synchronization.

0   0   2   03   (OX_SYNC_BALL)