A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00E70005 DSNXGSPL M700 with CREATE or ALTER PROCEDURE when the procedure body contains an IF statement which meets the pattern in the following example: CREATE PROCEDURE MYPROC1(INOUT P1 INT) LANGUAGE SQL P1:BEGIN IF 1=1 OR 2=2 THEN SELECT 1231 INTO P1 FROM SYSIBM.SYSDUMMY1; END IF; END P1! END IF; Additional Keywords: SQLSP SQLSTOREDPROC
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: * * All DB2 11 for z/OS, DB2 12 for z/OS users * * of native SQL PL procedue, compiled SQL * * scalar function, Advanced trigger which * * contains always true predicate in its * * control statement. * **************************************************************** * PROBLEM DESCRIPTION: * * An ABEND04E RC00E70005 at location * * DSNXGRDS DSNXGSPL M700 may occur when * * a native SQL PL procedure, compiled * * SQL scalar function, Advanced trigger * * contains a control statement * * satisfies the following * * condition: * * 1. It contains always true predicate, * * like 1=1. * * 2. The always true predicate is under * * OR boolean term. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** The control statement satisfies the following conditions: 1. It contains always true predicate, like 1=1. 2. The always true predicate is under OR boolean term. The following example could recreate the ABEND: CREATE PROCEDURE MYPROC1(INOUT P1 INT) LANGUAGE SQL P1:BEGIN IF 1=1 OR P1=2 THEN SELECT 1231 INTO P1 FROM SYSIBM.SYSDUMMY1; END IF; END P1! DB2 abend because it doesn't handle the always true predicate correctly.
Problem conclusion
DB2 is updated to handle the always true predicate correctly in SQL PL procedure, compiled SQL scalar function and advanced trigger. Additional Keywords: SQLNATIVESQLPL SQLUDF SQLTRIGGER
Temporary fix
Comments
APAR Information
APAR number
PI90322
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-11-17
Closed date
2018-01-10
Last modified date
2018-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI53121 UI53123
Modules/Macros
DSNXOYPC
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 February 2018