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:

1. The log from the SAS session includes the customary final note with the total CPU and memory used by the SAS session.
2. The job is not consuming any CPU and is still considered active by the system.
3. 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

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: