STOP command: Stopping a Horizon CNOS remote or session group

Summary

Privileges

User 0, system administrator, system manager

Function

Stops a remote or session group

Syntax

STOP {REMOTE | SESSIONGROUP} entityname

Where: entityname is the name specified on the DEFINE REMOTE or DEFINE SESSIONGROUP command.

Usage notes

The STOP command stops the specified remote or sessiongroup.

If the STOP command is issued when there are active users of the specified entity, the entity is put in a drain state in which new users are prevented from using the entity. Active users are allowed to continue until their current conversations end.

If the STOP command is issued while there are no active users of the specified entity, the entity is completely stopped.

STOP REMOTE has the following effects:

• Causes an orderly shutdown of all sessions associated with the remote. This consists of:

  • Resetting to zero the session limits for all session groups associated with that remote

  • Rejecting new conversation requests

  • Unbinding all sessions associated with the remote

• Frees any storage acquired for session management

• Preserves remote and sessiongroup entity definitions

STOP SESSIONGROUP has the same effects on a single session group as STOP REMOTE has on all the session groups for a remote, except that STOP SESSIONGROUP does not free any storage acquired for session management.

Once stopped, you can restart a session group by using START SESSIONGROUP. A stopped sessiongroup is also restarted implicitly by the next request for a conversation using that CNOS connection. Restarting a sessiongroup causes a renegotiation of the session limits and contention winners between the LUs sharing the sessions.

Unlike STOP PROCESSGROUP, STOP REMOTE does not unlock the remote definition. You cannot redefine this entity by issuing a new DEFINE command for it during the Model 204 run.