Problem Note 57665: An 0C4 abend might occur when you are accessing a DB2 table after applying Hot Fix S60002
 |  |  |  |  |
After Hot Fix S60002 has been applied, an 0C4 abend might occur when the following is true:
- A DB2 LIBNAME engine is used to access a DB2 table
- The DBKEY= data set option is specified with two or more variables
- At least one of the variables specified with the DBKEY= option is defined as NOT NULL
- The LIBNAME or data set option DBNULLKEYS= is not included or is explicitly set to YES if included
The error might look similar to the following:
ERROR: System abend 0C4 occurred in module SASIODB2 function
db2m_fetch_init at offset 0001DC.
ERROR: Traceback will be attempted...
NOTE: Traceback called
NOTE: Module Function Offset Line
NOTE: -------- -------- ------ ----
NOTE: SASXDBI YOEGET 0010D2 0
NOTE: SASYOIO YOGET 0004BC 0
NOTE: SASSQX @@271913 00052C 0 sqxsrc_get_next
NOTE: SASSQX @@455728 000410 0 sqxjndx_get_next
NOTE: SASSQX @@669285 00040E 0 sqxcrta_get_next
NOTE: SASSQX @@669271 0011EE 0 sqxcrta_open
NOTE: SASSQX @@669257 0001D0 0 sqxcrta_init
NOTE: SASSQX SQXEXEC 000136 0
NOTE: SASSQX SQLLOOP 000EF2 0
NOTE: SASSQL SASSQL 000312 0
NOTE: SASHOST UNKNOWN 002E24 0
ERROR: Delete current task.The only workaround is to explicitly include DBNULLKEYS=NO in the LIBNAME statement or as a data set option if the transaction table does not include any missing values.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to DB2 | z/OS | 9.4 TS1M1 | 9.4 TS1M2 |
A fix for this issue for SAS/ACCESS Interface to DB2 9.4_M1 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/S60.html#57665| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2016-03-07 11:38:05 |
| Date Created: | 2016-02-16 09:31:50 |