IBM Support

PH53901: ENHANCEMENT OF MESSAGE WHEN HPU TERMINATES IN USER ABEND.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Enhancement of message when HPU terminates in USER ABEND.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Db2 High Performance Unload         *
    *                 for z/OS                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When Db2 HPU terminates in user abend,  *
    *                      it issues an INZZ001S message to notify *
    *                      the user. As the Language environment   *
    *                      subsequently cancels all the active     *
    *                      threads in ABENDS222, many other        *
    *                      INZZ001S messages are also issued to    *
    *                      inform about the ABENDS222.             *
    *                                                              *
    *                      Although the user abend occurs first,   *
    *                      the related INZZ001S messages might not *
    *                      be issued before the INZZ001S messages  *
    *                      issued for the non meaningful ABENDU222 *
    *                      that are only consequences of the user  *
    *                      abend as in the example below:          *
    *                                                              *
    *                      INZZ001S(0001): ABEND IN ********       *
    *                           - CODE=S422 U0000 REASON=000001A0  *
    *                      INZZ002I(0001): NO DUMP REQUESTED       *
    *                      INZZ001S(0002): ABEND IN ********       *
    *                           - CODE=S422 U0000 REASON=000001A0  *
    *                      INZZ002I(0002): NO DUMP REQUESTED       *
    *                      INZZ001S(0003): ABEND IN ********       *
    *                           - CODE=S422 U0000 REASON=000001A0  *
    *                      INZZ002I(0003): NO DUMP REQUESTED       *
    *                      INZZ001S(0004): ABEND IN ********       *
    *                           - CODE=S422 U0000 REASON=000001A0  *
    *                      INZZ002I(0004): NO DUMP REQUESTED       *
    *                      INZZ001S(0005): ABEND IN ********       *
    *                           - CODE=S422 U0000 REASON=000001A0  *
    *                      INZZ002I(0005): NO DUMP REQUESTED       *
    *                      INZZ001S(0006): ABEND IN ********       *
    *                           - CODE=S422 U0000 REASON=000001A0  *
    *                      INZZ002I(0006): NO DUMP REQUESTED       *
    *                      .                                       *
    *                      .                                       *
    *                      INZZ001S(0100): ABEND IN BPXPTATT       *
    *                           - CODE=S000 U1136 REASON=0000005F  *
    *                      .                                       *
    *                      IEF450I MSPIA100 HPU STEP01             *
    *                      - ABEND=S422 U0000 REASON=000001A0  814 *
    *                                                              *
    *                      This is misleading and makes the        *
    *                      finding of the root cause of the        *
    *                      termination of the unload difficult.    *
    *                      Db2 HPU should make sure to issue a     *
    *                      dedicated console message to report the *
    *                      situation that requires a user abend    *
    *                      before actually abending the unload so  *
    *                      that this message is displayed before   *
    *                      any other message related to abends.    *
    *                      To make the troubleshooting by the IBM  *
    *                      support easier, this message should     *
    *                      also provide more information about the *
    *                      context of the occurrence of the user   *
    *                      abend.                                  *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    Put the focus on user abend as root cause of the termination by
    issuing an early dedicated message
    

Problem conclusion

  • Code has been changed to fix this problem
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH53901

  • Reported component name

    DB2 HI PERF UNL

  • Reported component ID

    5697F4400

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-04-13

  • Closed date

    2023-04-20

  • Last modified date

    2023-05-03

  • 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

  • R510 PSY UI91518

       UP23/04/26 P F304

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

Document Information

Modified date:
03 May 2023