A fix is available
APAR status
Closed as program error.
Error description
ABEND04E RC00C90101 at DSNOGETD 5007 is issued when lob string processing gets RESOURCE UNAVAILABLE error.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All DB2 10 for z/OS users of LOBs when * * used in a LIKE predicate. * **************************************************************** * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at DSNOGETD 5007 * * can occur for a LOB column, defined in * * a UNICODE table, is used in a LIKE * * predicate when a 'resource unavailable' * * condition is detected. Instead DB2 * * should issue SQLCODE -904 for 'resource * * unavailable' condition. * **************************************************************** * RECOMMENDATION: * **************************************************************** An ABEND04E RC00C90101 can occur at location DSNOGETD 5007 (ERQUAL5007) when processing a LOB column (in a UNICODE table) used in a LIKE predicate, a 'resource unavailable' condition is detected. Instead DB2 should issue SQLCODE -904 for the 'resource unavailable' condition. The following example illustrates the problem. 1. Create a UNICODE Table with a LOB column and insert a row. CREATE TABLE T1 (C1 CLOB(1K) , ID INT) CCSID UNICODE; INSERT INTO T1 VALUES(CLOB('ABCDE20'),1); 2. Issue a SELECT statement which uses the LOB column C1 in a LIKE predicate. SELECT * FROM T1 WHERE C1 LIKE '_E_'; During the LIKE predicate processing for the LOB, if a 'resource unavailable' condition is detected at the same time (let's say on behalf of the SELECT job being canceled by the user), the LOB processing code does not handle the unexpected error condition correctly which leads to the aforementioned abend. Please note, other SQL errors during UNICODE LOB LIKE predicate processing can also trigger the above abend.
Problem conclusion
The code in DB2 has been modified to prevent the abend for the stated conditions. After this fix a correct SQLCODE will be issued instead of ABEND04E. Additional Keywords: DB2LOB SQLLOB SQLLIKE SQLCODE904
Temporary fix
Comments
APAR Information
APAR number
PM80983
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-20
Closed date
2013-04-19
Last modified date
2013-06-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK93653
Modules/Macros
DSNOUL16 DSNOUL8
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK93653
UP13/05/07 P F305
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":"10.1","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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 June 2013