IBM Support

PH65321: IMPROPER ERROR-FREE RETURN CODE DESPITE PREMATURE TERMINATION OF THE THREAD FOR LOCK TABLE BEFORE THE COMPLETION OF THE UNLOAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A logical unload unduly completes with a normal completion code
    (i.e. less than 8) and produces unloaded data that does not
    have the consistency requested by the LOCK YES option (or the
    SHRLEVEL REFERENCE option for the alternate unload tools
    emulated by Db2 HPU).
    This occurs if the thread Db2 HPU opens to perform the LOCK of
    the table requested by the unload statement abnormally ends
    before of the unload completes e.g. because it has been
    canceled or because the concerned Db2 subsystem/data sharing
    group has been stopped.
    
    Although Db2 HPU reports a failure when attempting to close the
    thread in question with a message as follows:
    INZI193E DB2 ERROR: FROM CLI   : {DB2 FOR OS/390}{ODBC
    DRIVER}{DSN12015}
              DSNT408I SQLCODE = -924, ERROR:  DB2 CONNECTION
              INTERNAL ERROR, 0001, 0100
                       00F30018
              DSNT418I SQLSTATE   = 58006 SQLSTATE RETURN CODE
              DSNT415I SQLERRP    = DSNAET03 SQL PROCEDURE
              DETECTING ERROR
               ERRLOC=5:10:2
    INZI193E DB2 ERROR: FROM SQLCA : SQLSTATE : 58006 SQLCODE : -924
    INZI193E DB2 ERROR: FROM SQLCA : DSNAET03
    INZI193E DB2 ERROR: FROM SQLCA : 0001.0100.00F30018
    it goes on unloading the data and does not end with an error
    completion code.
    

Local fix

  • Consider monitoring the Db2 HPU job to catch those issuing
    INZI193E and take an action to prevent the use of the data they
    have unloaded that might be inconsistent. A new run of a
    concerned job ending with a normal completion code and not
    issuing the INZI193E message solves the issue regarding the
    potential inconsistency if the unloaded data.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 High Performance Unload for     *
    *                 z/OS                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: A logical unload unduly completes with  *
    *                      a normal completion code (i.e. less     *
    *                      than 8) and produces unloaded data      *
    *                      that does not have the consistency      *
    *                      requested by the LOCK YES option (or    *
    *                      the SHRLEVEL REFERENCE option for the   *
    *                      alternate unload tools emulated by Db2  *
    *                      HPU).                                   *
    *                      This occurs if the thread Db2 HPU       *
    *                      opens to perform the LOCK of the table  *
    *                      requested by the unload statement       *
    *                      abnormally ends before of the unload    *
    *                      completes e.g. because it has been      *
    *                      canceled or because the concerned Db2   *
    *                      subsystem/data sharing group has been   *
    *                      stopped.                                *
    *                                                              *
    *                      Although Db2 HPU reports a failure      *
    *                      when attempting to close the thread in  *
    *                      question with a message as follows:     *
    *                      INZI193E DB2 ERROR: FROM CLI   : {DB2   *
    *                      FOR OS/390}{ODBC DRIVER}{DSN12015}      *
    *                                DSNT408I SQLCODE = -924,      *
    *                                ERROR:  DB2 CONNECTION        *
    *                                INTERNAL ERROR, 0001, 0100    *
    *                                00F30018                      *
    *                                DSNT418I SQLSTATE   = 58006   *
    *                                SQLSTATE RETURN CODE          *
    *                                DSNT415I SQLERRP    =         *
    *                                DSNAET03 SQL PROCEDURE        *
    *                                DETECTING ERROR               *
    *                                 ERRLOC=5:10:2                *
    *                      INZI193E DB2 ERROR: FROM SQLCA :        *
    *                      SQLSTATE : 58006 SQLCODE : -924         *
    *                      INZI193E DB2 ERROR: FROM SQLCA :        *
    *                      DSNAET03                                *
    *                      INZI193E DB2 ERROR: FROM SQLCA :        *
    *                      0001.0100.00F30018                      *
    *                      it goes on unloading the data and does  *
    *                      not end with an error completion code.  *
    *                                                              *
    *                      Local fix : consider monitoring the     *
    *                      Db2 HPU job to catch those issuing      *
    *                      INZI193E and take an action to prevent  *
    *                      the use of the data they have unloaded  *
    *                      that might be inconsistent. A new run   *
    *                      of a concerned job ending with a        *
    *                      normal completion code and not issuing  *
    *                      the INZI193E message solves the issue   *
    *                      regarding the potential inconsistency   *
    *                      if the unloaded data.                   *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    improper error-free return code despite  premature termination
    of the thread for LOCK TABLE before the completion of the unload
    

Problem conclusion

  • Code has been changed to fix this problem
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65321

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-02-18

  • Closed date

    2025-04-07

  • Last modified date

    2025-05-02

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

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

Modules/Macros

  • INZUTILK
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R520 PSY UO02742

       UP25/04/09 P F504

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"520","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 May 2025