IBM Support

PI77049: SERVER IS ABLE TO RESTART AFTER ABENDDC3 RC 0A150001 WHEN IT SHOULDN'T

Fixes are available

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This abend means a WebSphere Application Server for z/OS
    attempted to change code levels for a node that still has
    servers active at a different code level.  The suggested action
    for this is to change the server to use the same code level as
    the other servers in the node, or bring down the other servers
    in the node and change them to use the same code level as the
    server that failed to start, then restart the server(s).  But
    in this case, a restart of the server works, even when the
    suggested action hasn't been done.  This is because a use count
    is incorrectly decremented after the abendDC3 RC 0A150001 which
    allows the server to restart.  A restart of the server should
    still fail with the abendDC3 RC 0A150001 if the suggested
    action hasn't been done.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 and V9.0 for z/OS               *
    ****************************************************************
    * PROBLEM DESCRIPTION: A WebSphere Application Server for      *
    *                      z/OS server is able start even though   *
    *                      it is at a different code level than    *
    *                      the other servers in the node.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After failing to start because of an ABENDDC3/ABENDSDC3 reason
    code 0A150001, a server is able to start even though it is at a
    different code level than the other servers in the node.
    This is because a use count was incorrectly decremented when
    the server hit the DC3 abend with a reason code 0A150001.
    When none of the suggested actions for the abend and reason
    code are performed, a restart of the server should still
    fail with an abend DC3 reason code 0A150001 because it is
    still at a different code level than other servers in the node.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI77049

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-22

  • Closed date

    2017-03-15

  • Last modified date

    2017-03-15

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

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 December 2021