When using SAS/ACCESS Interface to Sybase, if an error such as in the prepare, execute, or fetch is generated and not returned to the SAS supervisor, all of the data for that particular thread is not being brought into SAS because that thread is dead from the error message.

A similar scenario is where one thread is not returning any rows and an error condition is not being raised to terminate processing and return an error condition to the user, by limiting the Sybase server to 6 connections, but requesting 7, which causes one of the threads to have a connection failure.

The problem was in the threaded error routine, where it was trying to create a temporary command handle allocation that was a de-referenced null pointer.

After applying the fix, you will have an error message returned back to the supervisor which is written out to the SAS log.

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: