PI38990: DB2 SUBSYSTEM ABEND S004F/00E50702 AFTER MORE THAN 6 RETRIES ON DBAT ABEND 0C4-3B FROM DSNLXRSS

Obtain the fix for this APAR.

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 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

• RA10 PSY UI33609

     UP15/12/30 P F512

• RB10 PSY UI33610

     UP15/12/30 P F512

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.