Subsequent steps might still be executed when you are running a query in a z/OS operating environment when the following conditions exist:

• The DB2 query results in a deadlock and a -913 error is issued.
• The system option DB2RRS is specified.

In addition, to the job continuing to process, the job return code might still be 0. The DB2 error might look similar to the following:

DB2 ERROR:
RESULT OF SQL STATEMENT:
DSN00913E UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON CODE 00C9008E,
TYPE OF RESOURCE 00000D01, AND RESOURCE NAME 00000285.00013904
A DUMP OF THE SQLCA FOR THE GET DIAGNOSTICS REQUEST FOLLOWS:
           ROW NUMBER: 0 ERROR CONDITION: 1 REASON CODE: 13172878
           SQLCODE: -913 SQLSTATE: 57033 SQLERRP: DSNXRUP2

There is no workaround for this issue other than not using the system option DB2RRS.

Operating System and Release Information

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