Problem Note 36446: SAS® session intermittently becomes non-responsive upon SAS termination
In rare instances, a SAS job becomes unresponsive in the module SASTK during clean-up and termination processing.
The following indicators are typical of this problem:
- The log from the SAS session includes the customary final note with the total CPU and memory used by the SAS session.
- The job is not consuming any CPU and is still considered active by the system.
- If the job is left active for the inactive timeout interval set on your system, it might terminate with a system abend 522.
If you rerun the job, it will usually terminate normally.
One possible cause of this problem is when the SAS task is interrupted by an external clock interrupt.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | Base SAS | z/OS | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
SASTK stops responding during SAS termination, but the SAS log indicates that the job completed normally.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2009-07-22 09:06:16 |
| Date Created: | 2009-07-02 17:01:27 |
