Using SAS/ACCESS^® Interface to DB2 on z/OS with the BULKLOAD=YES option to load a character variable that is missing in SAS into an existing DB2 table, whose corresponding variable has been defined as NOT NULL or NOT NULL WITH DEFAULT, results in the incorrect data being inserted. When the SAS variable is missing and the DBMS variable is defined as not accepting NULLS, the value stored in data set option NULLCHARVAL= should be used, instead of either the default blank or what it was explicitly set to being used. An incorrect value of a '80'x for the first character followed by '00'x for the rest of the characters up to the full length of the field is inserted.

For example, if a variable is defined as CHAR(8) that does not allow NULLS and the variable in SAS is missing, what gets inserted is '8000000000000000'x (hexadecimal '80' followed by 7 nulls) instead of the correct value '4040404040404040'x (8 blanks).

There is no workaround 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:

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