In some situations an abnormal ending with an S0C4 abend code might occur during SAS termination. The SAS log for the job might indicate that the abnormal ending occurs in the SASHOST, SASXA1, or SASXAL modules, depending on the entry module that is being used.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	Base SAS	z/OS	9.1 TS1M3 SP4

* 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.

---

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

---

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

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

---

A fix for SAS 9.2 (TS1M0) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/f9_sbcs_prod_list.html#032798

---

A fix for SAS 9.2 (TS1M0) with Asian Language Support (DBCS) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/f9_dbcs_prod_list.html#032798

---

SASLOG reflects that processing was complete. JOBLOG shows that an abend S0C4 occured in SASHOST, SASXA1 or SASXAL. System dump will show abend in csect VMALCP(VMALCP).

Type:	Problem Note
Priority:	high

Date Modified:	2008-12-18 09:53:57
Date Created:	2008-07-28 13:09:30