IBM Support

PI35935: DURING BATCH EXECUTION IN FETCH USING SCROLLABLE INSENSITIVE CURSOR - AN INCORRECT SQLCODE100 WAS RECEIVED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During batch execution in fetch using a scrollable insensitive
    cursor, an incorrect SQLCODE +100 was received.
    
    DSNT404I SQLCODE = 100, NOT FOUND:  ROW NOT FOUND FOR FETCH,
    UPDATE, OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE
    
    The SQLCODE+100 depends on the number of records returned by the
    cursor (with 4 million records the problem does not occur, but
    it does with 7 million), so it does not depend on a specific
    record.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 zOS v10 and v11 INSENSITIVE or       *
    *                 SENSITIVE STATIC scrollable cursor users     *
    *                 of backward scan on a result set that is     *
    *                 stored in multiple partitions.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect results may be returned on    *
    *                      backward scans for INSENSITIVE or       *
    *                      SENSITIVE STATIC scrollable             *
    *                      cursors.  SQLCODE +100 is returned      *
    *                      incorrectly.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using INSENSITIVE or SENSITIVE STATIC scrollable cursor
    and fetching data backward on data that is stored in more than
    1 partition in the workfile. Incorrect end of file (top of file
    for backward scan) is detected, because the partition number
    is not considered.
    

Problem conclusion

  • DB2 code is fixed to consider the partition number in the end
    of file (top of file) checking code.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI35935

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-26

  • Closed date

    2015-06-30

  • Last modified date

    2015-08-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI28984 UI28985

Modules/Macros

  •    DSNILAST
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI28984

       UP15/07/15 P F507 Ž

  • RB10 PSY UI28985

       UP15/07/15 P F507 Ž

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
06 May 2020