Use the stop command to initiate an orderly Connect:Direct® server shutdown sequence or forcibly terminate the software. Connect:Direct will not run new Processes and will not establish new connections with remote systems. You can issue commands and users can sign on until the server terminates. You must identify the type of stop or an error message is generated.
The format for the stop command follows.
|stop||[force | immediate | step| quiesce]|
Choose one of the following options listed in order of severity:
|force||Forcibly terminates the Connect:Direct server with no attempt to terminate executing Processes in an orderly fashion or write statistics to disk. Connect:Direct releases all server resources, including connections, LU 6.2 sessions, memory, and semaphores. It retains all active Processes in the TCQ and restarts them when you restart the Connect:Direct server.|
|immediate||Begins an immediate, but orderly, shutdown of all activity and terminates Connect:Direct. The software terminates connections, writes statistics records, closes files, and shuts down. It retains all active Processes in the TCQ and restarts them when you restart the Connect:Direct server.|
|step||Shuts down Connect:Direct after all currently executing Process steps complete. The software writes statistics records, closes files, and shuts down. To restart Processes at the next step the next time you start Connect:Direct, set the tcq.start initialization parameter to require a warm start.|
|quiesce||Runs all executing Processes to completion. Connect:Direct starts no new Processes.|
The following command forcibly terminates Connect:Direct and returns control to the operating system.