Using the READBUFF= data set or LIBNAME option with SAS/ACCESS® Interface to DB2 on a z/OS system might result in a data integrity issue. The issue occurs when a new variable is created and assigned a constant value. If the constant is located after a character variable in the SELECT clause, every N observations (where N is the READBUFF= setting) of the data become corrupted. If the constant is located after a numeric variable, then the constant value becomes corrupted starting at obs 1 and then at every N observations.

Here is an example. Say that you run a query where the READBUFF= option is set to 10 and the constant is located after a character variable. That character variable on rows 10, 20, 30 (and so on) would become corrupted. And if the constant is located after a numeric variable, that constant value on rows 1, 11, 21 (and so on) would become corrupted.

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

Operating System and Release Information

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

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