Problem Note 8508: Specifying a composite index with DBKEY= may cause a S0C4 abend
If you specify the DBKEY= data set option with a composite key (whether
or not there is an actual index on the DBMS) and at least one of the
fields is defined as NOT NULL, a S0C4 abend will occur.
ERROR: System abend 0C4 occurred in function D2GETI at offset 0000FA.
ERROR: Traceback will be attempted...
ERROR: Function offset
ERROR: -------- ------
ERROR: YOEGET 000756
ERROR: .©.åØ&.j 000164
ERROR: DSISKR 00024E
ERROR: VGCPGM0 0000F8
ERROR: VGEXEC 00007A
ERROR: DSXXEXC 0000D0
ERROR: DSEXEC 00007E
ERROR: SASDS 00038A
ERROR: Delete current task.
There is no known workaround at this time.
Reference SAS note #006736 to find information on a hotfix that is
needed to allow composite indexes to work in situations other than the
one above.
A Technical Support hot fix for Release 8.2 TSLEVEL TS2M0 for this
issue is available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#008508
Operating System and Release Information
| Product Family | Product | System | Reported Release | Fixed Release* |
| SAS System | SAS/ACCESS Interface to DB2 | z/OS | 8.2 TS2M0 | 9.1 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Data Sources ==> External Databases ==> DB2
SAS Reference ==> LIBNAME Engines
|
| Date Modified: | 2002-10-28 16:30:06 |
| Date Created: | 2002-09-20 12:28:36 |
