A fix is available
APAR status
Closed as program error.
Error description
ABEND0C4 RC11 at DSNXOP0 OFFSET196D4 occurs for a query that contains CURRENT_SERVER or CURRENT_TIMEZONE and another special register. Here is an example: SELECT CURRENT_TIMEZONE ,CURRENT TIMESTAMP FROM SYSIBM.SYSDUMMY1 ; Additional symptoms: 1. ABEND04E RC00E70005 at DSNXOP1 M150 2. ABEND0C4 RC04 at DSNHSM1 OFFSET066D4
Local fix
Delimit CURRENT_SERVER or CURRENT_TIMEZONE if they are column names. Or remove PTF UI60025 if delimiting is not possible.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 12 for z/OS users of SQL statements * * containing a special register and who have * * PH02646/UI60025 applied. * **************************************************************** * PROBLEM DESCRIPTION: * * An ABEND0C4 RC00000011 at DSNXGRDS * * DSNXOP0 OFFSET 196F4 , ABEND04E * * RC00E70005 in DSNXGRDS DSNXOP1 M150, * * or ABEND0C4 RC00000004 at DSNXPA * * DSNHSM1 OFFSET 066D4 can occur when * * an SQL statement satisfies the * * following conditions: * * 1. it contains CURRENT_SERVER or * * CURRENT_TIMEZONE identifier * * 2. it contains a special register * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** The following example could recreate the ABEND: CREATE TABLE T1(CURRENT_SERVER INT, C2 CHAR(5)); SELECT CURRENT_SERVER, CURRENT TIMESTAMP FROM T1; DB2 abends when process the SELECT statement. This APAR is a fixing APAR for PH02646/UI60025.
Problem conclusion
Db2 is updated to handle the aforementioned SQL statement correctly. Additional Keywords: SQLSPECIALREG
Temporary fix
Comments
APAR Information
APAR number
PH07393
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-01-16
Closed date
2019-02-15
Last modified date
2019-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI61327
Modules/Macros
DSNHXLTR DSNXOFN3 DSNHSYMH DSNHSM2P DSNXOLV DSNDQW05 DSNHSM2V DSNHAPLY DSNHPTAB DSNHSM5T
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI61327
UP19/03/02 P F903 {
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":"12.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":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 April 2019