Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

The SAS/Connect spawner may hang while occupying it's port (and not
responding to any requests) when a client executes a LIBNAME statement
with SLIBREF while pointing to the spawner without a prior SIGNON.  This
happens when spawner port name is used.

Following is the example of the erroneous code

   %let mvs=test.mvs.com;
   options comamid=tcp remote=mvs;
   libname abc slibref=abc server=mvs.spawner;

To get the spawner working again and to free the spawner's port, the
local SAS client session or the spawner itself must be restarted.

The circumvention is to use the spawner's port number instead of the
port name. Using the following example the spawner will not hang and the
client program will end with error - as expected.

   %let mvs=test.mvs.com 7130;
   options comamid=tcp remote=mvs;
   signon mvs user=_prompt_ pw=_prompt_;
   signoff;
   libname abc slibref=abc server=mvs;


A Technical Support hot fix for Release 8.2 (TS2M0) for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#011433

For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#011433


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#011433

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#011433

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :