Incorrect results might occur when the following conditions exist in your SQL procedure query:

• You are using the LIBNAME engine to access DB2 under z/OS
• You are using the DBSASTYPE= data set option to convert a DB2 TIMESTAMP variable to a character variable
• You are using the READBUFF= LIBNAME or data set option

The only workaround is to change the query such that one of the above conditions is not part of the query.

Click the Hot Fix tab in this note to access the hot fix for this issue. After applying the hot fix, the READBUFF= setting will be set back to 1 so processing of the data type conversion can be done as specified with the DBSASTYPE= data set option.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to DB2 9.4_M2 is available at:

A fix for this issue for SAS/ACCESS Interface to DB2 9.4_M1 is available at:

A fix for this issue for SAS/ACCESS Interface to DB2 9.3_M2 is available at: