Usage Note 14174: Support status for running DB2 Version 8 in the z/OS operating environment
Currently, there are no known SAS issues when you run DB2 Version 8 in new-function mode with SAS® 8.2 (TS2M0) or any later SAS releases. However, running DB2 Version 8 with the third maintenance release for SAS 9.2 (TS2M3) works only when it is run in new-function mode. Attempting to run in compatibility mode results in an error similar to the following:
NOTE: The SAS System stopped processing this step because of errors.
No additional information is given as to what caused the error. There is no workaround for the issue.
The support for the longer names and longer statements that was added in DB2 Version 8 is support in SAS 9.2 and in SAS 9.1.3 with a hot fix.
However, there are some IBM issues with DB2 Version 8 that might occur when you use SAS. These are not SAS issues, though, because errors still occur outside of SAS. For example, an error occurs when you call a stored procedure under z/OS 1.6. In SAS, bulk loading also causes an error because SAS calls the DB2 load utility. SAS produces an S04E abend, but nothing else appears in the SAS log. When the call is made, for example through the DB2 Command-Line Processor, the DB2 reason code is 00E00079 with no S04E abend.
There is a PTF for this issue, UQ89412. However, this PTF causes the following additional APARS:
RUNSTATS TABLESPACE ... PART x INDEX ( aaaa PART x KEYCARD ) TABLE ALL
SHRLEVEL REFERENCE REPORT YES UPDATE NONE incorrectly updates Catalog.
COLCARD in SYSIBM.SYSCOLUMNS was updated with wrong value.
SQLCODE-413 from DSNXOLTH occurs when submitting a query which
references to a view with a CASE expr and an arithmetic expr
on a Smallint column. The following is a failed testcase:
CREATE VIEW U810034.TEST0002 (EMPNO, EDLEVEL) AS
CASE WHEN EDLEVEL=0 THEN 0
ELSE EDLEVEL + 190000 END AS EDLEVEL
SELECT * FROM U810034.TEST0002 WHERE EDLEVEL > 190001;
Operating System and Release Information
SAS/ACCESS Interface to DB2
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at: