A fix is available
APAR status
Closed as program error.
Error description
DB2DDF Defect pi38990 dpi38990 A DB2 DDF thread (DBAT) receiving multiple abend 0C4-3B from DSNLXLLM.DSNLXRSS when client sending invalid QID. After 6 retry attempts for this DBAT, DB2 abended with S004F-00E50702. The following message may be seen in the DB2mstr started task log, the corresponding event is recorded in logrec/erep showing DSNLXLLM.DSNLXRSS. ABND=04E-00D3440B DSNLXLLM.DSNLXGCS 0001 may be seen when client sends invalid QID *************************************************************** Additional Symptoms and Keywords: ABEND0C4 AB0C4 S00C4 0C4 0C4-0000003B 0000003B RC0000003B DSNLXLLM.DSNLXRSS DSNLXLLM DSNLXRSS ABEND04E AB04E S004E 04E 04E-00D3440B 00D3440B RC00D3440B DSNLXGCS DSNLXGCS:0001 0001 ABNDID0001 VRADC0001 ABEND04F AB04F S004F 04F DSNV086E MSGDSNV086E 00E05702 RC00E05702
Local fix
no local fix/workaround
Problem summary
**************************************************************** * USERS AFFECTED: All Distributed Data Facility (DDF) users. * **************************************************************** * PROBLEM DESCRIPTION: The following symptoms may appear on * * a DB2 for z/OS server during the * * processing of fetch or positioned * * update/delete: * * * * 1. DB2 subsystem termination with RC * * 00E50702 after multiple 0C4- * * 0000003B abends from DSNLXRSS * * * * 2. Abend 04E-00D3440B at * * DSNLXLLM.DSNLXGCS:0001 * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 for z/OS server may terminate with RC 00E50702 during the processing of fetch or positioned update/delete if a remote requester flows an SQL statement with a bad cursor identifier. Bad cursor identifiers will result in the multiple 0C4 abends in DSNLXRSS during repeated validation and retry processing. DB2 limits the number of retries and once the retry limit is exceeded, DB2 will terminate. The DB2 for z/OS server may also abend 04E-00D3440B at DSNLXLLM. DSNLXGCS:0001 during fetch processing if the remote requester flows in an SQL statement with a bad cursor identifier.
Problem conclusion
DB2 for z/OS server processing has been changed to return a parameter not supported reply when an invalid cursor identifier is received.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI38990
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2015-04-13
Closed date
2015-12-08
Last modified date
2016-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI33609 UI33610
Modules/Macros
DSNLXCQS DSNLXGCS DSNLXHIM DSNLXHNO DSNLXOQS DSNLXPRS DSNLXRSS DSNLXSSR DSNLXXSS DSNLZGDT DSNLZSDT
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":"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 January 2016