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

A client task with remote connections can hang or terminate abnormally
during SAS termination. During SAS termination processing, SAS will
attempt to cleanup various resources it believes are still allocated.
Among these are open remote connections. Due to timing it is possible
that a connection has not completely closed when SAS termination
processing occurs. The type of failure is dependant on how far along
the close of the connection is.

The symptoms which identify this are as follows; an abend in SASVTCP or
the JOB in an undetected WAIT state and the SAS Log reflecting the
closing note of:

    NOTE: The SAS session used ...

A circumvention to this problem until the HOTFIX can be installed is to
add a DATA Step to delay SAS termination until all SIGNOFF's have been
issued.

An example of giving 5 seconds delay for various hosts:

For z/OS Client:
    DATA _NULL_;
     x=SLEEP(5000);
    RUN;

For UNIX Client:
    DATA _NULL_;
     CALL SLEEP(5000,.001);
    RUN;

For Windows Client:
    DATA _NULL_;
     x=SLEEP(5000,.001);
    RUN;

This would be inserted as the last step of the client program and should
be performed after all SIGNOFFs have executed.

*** NOTE *** Refer to the appropriate host Companion documentation for
proper use and coding of the SLEEP FUNCTION or CALL routines.

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#014656

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#014656

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) for this issue is available at:

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