IBM Support

PH51677: WEBSPHERE DAEMON ABEND=SCC3 REASON=C9C20008

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Starting two daemons causes a failure to attach to shared memory
    for at least one of them resulting in an ABEND of the daemon.
    

Local fix

  • Ensure that only one daemon is started at a time and make sure
    that it has completed start-up before starting other servers
    that might cause a daemon to be started.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V9.0 for z/OS                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABENDCC3/ABENDSCC3 reason code          *
    *                      C9C20008 in a WebSphere Application     *
    *                      Server for z/OS daemon.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    One of two daemons starting at the same time can get an
    abend CC3 reason code C9C20008 because it is not attached to
    the shared memory that was allocated by the other daemon.
    The area that did not get attached to is BBODBGVT_BBOAOCNP.
    Both daemons saw BBODBGVT_BBOAOCNP was zero and were trying to
    set it with CSG. The daemon where the CSG failed continued
    along without attaching to the area created by the other
    daemon.
    This can happen when WAS_DAEMON_ONLY_enable_adapter is set to
    true.
    

Problem conclusion

  • Changed the code to attach to the shared memory that was
    created by another daemon.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.16. For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH51677

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-01-03

  • Closed date

    2023-02-21

  • Last modified date

    2023-02-21

  • 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

[{"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":"900","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 February 2023