IBM Support

PI29771: AN ABEND DC3 REASON 000C0009 SURFACES AFTER ATTEMPTING TO START A CONTROL REGION AFTER AN IPL. SUBSEQUENT START IS SUCCESSFUL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An abend DC3 reason 000C0009 surfaces after attempting to start
    a control region after an IPL.  Subsequent start of the control
    region is successful.  The abend can surface for any control
    region such as the DeploymentMangager, Node Agent or
    Application server control regions.
    
    In addition to the abend the control region job output will
    show messages.
    
    Trace: 2014/10/30 13:54:34.583 02 t=8D2E88 c=UNK key=S2 tag=
    (95005138)
       Description: Throw CORBA system exception
       exception id: CORBA::INTERNAL
       minor code: c9c2580b
       from filename: ./bbgjutil.cpp
    
    Trace: 2014/10/30 13:54:34.619 02 t=8D2E88 c=UNK key=S2 tag=
    (8400E317)
       Description: Log Boss/390 Error
       from filename: ./bbgoctl.cpp
       at line: 791
       error message: BBOO0003E WEBSPHERE FOR Z/OS CONTROL PROCESS
    BBOS001 ENDED ABNORMALLY, REASON=C9C2580B.
    
    The problem is observed to happen when the server is brought up
    on a new respack.
    

Local fix

  • Restart the server that abended
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of WebSphere Application Server V8.0  *
    *                  and V8.5 who apply maintenance by mounting  *
    *                  the WebSphere Application Server binaries   *
    *                  to new underlying symbolic links            *
    ****************************************************************
    * PROBLEM DESCRIPTION: After re-mounting the symbolic links    *
    *                      to a new target location, the first     *
    *                      attempt to start the server fails.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The OSGi framework used by WAS 8 performs internal consistency
    checking upon launch.  Among those checks is a check to ensure
    that the underlying location of the system bundle has not
    changed.  When maintenance is applied by remounting the
    symbolic links for the server binaries to a new target
    location (as is sometimes done by z/OS users), this causes the
    consistency check to fail, and the framework exits with an
    error code that indicates that it needs to be restarted.
    Subsequent attempts to start the server will be
    successful, but the first attempt will fail unless the
    framework is explicitly started in "clean" mode, or the
    framework's cache is cleared prior to the start attempt.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI29771

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-11-17

  • Closed date

    2015-03-16

  • Last modified date

    2015-03-16

  • 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:
28 April 2022