If a SAS error or an SQL*Loader error occurs when you use SAS/ACCESS^® Interface to Oracle to bulk load on z/OS, an S0C4 abnormal ending might also occur within the SASVX or the SASVXSAM modules. The abnormal ending occurs because allocated memory has been freed within the error-handling functions, but the host application is not aware that this occurred. As a result, the host might attempt to free the storage again or to extract valid addresses from the freed area.

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 :