A hot fix has been developed to enable the SAS Workspace Server to detect when a client machine unexpectedly closes its connection.

Click the Hot Fix tab in this note to access this hot fix.

As a result of the new functionality, the SAS Workspace Server stops running automatically. For example, this behavior can occur when you use the Microsoft Windows Task Manager to kill a client such as SAS^® Enterprise Guide^®.

The SAS Workspace Server uses IOM.CurrentClients (an existing counter that has been updated) and IOM.ReconnectEnabled (a new information variable) to determine when a client unexpectedly closes its connection. The SAS Workspace Server only stops when it encounters the following parameters:

Note: in releases earlier than SAS^® 9.4, the IOM.ReconnectEnabled information variable is visible only when it is set to True. Starting in SAS 9.4, variable is visible whether it is set to True or False.

This functionality only applies to single-user standard SAS Workspace Servers. It does not apply to multiple-user servers such as pooled workspace servers or to the SAS^® Stored Process Server.

If you do not want the SAS Workspace Server to stop automatically in the situation described previously, you should set the environment variable WKSP_KILL_OFF. With the environment variable set, you can check the updated IOM.CurrentClients counter using SAS^® Management Console to determine whether orphan processes exist and dealt with at the discretion of the administrator.

• Case 0: IOM.CurrentClients=1 indicates that SAS Workspace Server has a client. YOu probably do not want to kill it.
• Case 1: IOM.CurrentClients=0 indicates that SAS Workspace Server has lost the client, so the process can be killed.
• Case 2: IOM.CurrentClients=0 IOM.ReconnectEnabled=False indicates that SAS Workspace Server has lost the client, so the process can be killed.
• Case 3: IOM.CurrentClients=0 IOM.ReconnectEnabled=True indicates that SAS Workspace Server has lost the client, but that client might be reconnected. So you might not want to kill this one yet.

Operating System and Release Information

A fix for this issue for Base SAS 9.21_M3 is available at:

A fix for this issue for Threaded Kernel IOM 9.3 is available at: