PH33878: ABEND04E RC00E2000F AT DSNLCBFM DSNSVSFB OFFSET00A2A CAN OCCUR DURING MULTI-ROW FETCH IN DISTRIBUTED ENVIRONMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND04E RC00E2000F at DSNLCBFM DSNSVSFB OFFSET00A2A can occur
  during multi-row fetch in distributed environment (DRDA fixed
  row protocol).
  The problem can occur when one of the columns being fetched has
  type TIMESTAMP WITH TIME ZONE.
  
  This problem is data-dependent, possibly occurring when the
  number of rows being fetched is high (>3000) and varying
  data-type values are at or near their maximum possible length.
  
  ADDITIONAL SYMPTOMS:
  1. Requester system can display DSNL031I message with REASON
  00D351FF and ERROR ID DSNLZRPA0001
  2. ABEND04E RC00E2000F DSNLCBFM DSNSVSFB +00A6A OFFSET00A6A
  3. The storage overlay at Server can result in additional
  symptoms depending on the storage overlaid.
  

Local fix

• Use block fetch for the query
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS users of multi-row                       *
  * fetch in a distributed environment.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * An ABEND04E RC00E2000F at DSNLCBFM                           *
  * DSNSVSFB OFFSET00A2A can occur when                          *
  * executing a query using MULTI-ROW                            *
  * FETCH in a distributed environment.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  An ABEND04E RC00E2000F at location DSNLCBFM DSNSVSFB
  OFFSET00A2A could/may/might occur during the execution of a
  query that uses MULTI-ROW FETCH in a distributed environment
  (DRDA fixed row protocol).
  The problem is known to occur when one of the columns being
  fetched during query execution is of the data type,
  TIMESTAMP WITH TIME ZONE. Db2 sets up an invalid length which
  can lead to a possible storage overlay or other symptoms.
  The following query helps to illustrate a failing example.
  SELECT BIGINT, TSTZ9, CHAR8A, CHAR8B, CHAR8C, CHAR8D, CHAR1,
         VARCHAR64
    FROM TEST
    ORDER BY BIGINT DESC;
  Please note: The column TSTZ9 is defined as follows,
  TIMESTAMP(9) WITH TIME ZONE NOT NULL.
  Furthermore, this problem is data-dependent, and can possibly
  occur when the number of rows being fetched is high, that is
  more than 3000, with varying data type values that are at or
  near their maximum possible length. Since the problem can
  result in a storage overlay, other symptoms are also possible.
  

Problem conclusion

• Db2 bind time has been modified to set up the correct length
  for the TIMESTAMP WITH TIME ZONE column so that if it is
  referenced during a multi-row fetch in a distributed
  environment, the overlay and/or reported storage abend will
  not occur, allowing the query to complete normally.
  Additional Keywords: SQLMULTIROW SQLFETCH DB2DRDA
                       SQLTIMESTAMPTZ DB2OVRLAY/K SMCOVERLAY
  

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:

  UI74810

Modules/Macros

• DSNXGRTM DSNXGOU2
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI74810

     UP21/04/15 P F104 ¢

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.