IBM Support

PM51888: Controller Region terminates with abend code S9C6 or S0C2 during startup

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Symptom 1:
    The thread that received the 9C6 shows the following:
    
    Traceback:
    
    DSA      Entry       E  Offset  Statement   Load Mod
    1        BBOG_LogRequestTable::obtainLatch(int,char(&).8.)
    -3DB31A54              *PATHNAM
    2
    BBOG_FailureMonitor::processRecoveryLogRequest(bbogsrdd*)
    +00000256              *PATHNAM
    3        BBOG_FailureMonitor::processACRW(acrwObj&)
    +000000D6              *PATHNAM
    4
    ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
    +00000C3C              *PATHNAM
    5        ACR_ExecutionRoutine
    +0000020C              *PATHNAM
    6        CEEVROND    +000011F4              CEEPLPKA
    7        CEEOPCMM    +000009A2              CEEBINIT
    
    ----------------------------------------------------------------
    Symptom 2:
    
    Abend 0C2 in Java code zip inflater.  Top of the traceback for
    the failing thread:
    
    Native traceback:
    __zerro
    __zerros
    CEEVROND
    CEEHDSP
    CEEHRNUH
    inflate_blocks_reset
    inflateReset
    Java_java_util_zip_Inflater_reset
    ...
    
    Java traceback:
    at java/util/zip/Inflater.reset(Native Method)
    at java/util/zip/Inflater.reset(Inflater.java:328
    at java/util/zip/ZipFile.releaseInflater(ZipFile.java:281
    at java/util/zip/ZipFile.access$000(ZipFile.java:30
    at java/util/zip/ZipFile$1.close(ZipFile.java:218
    
    With HEAPCHK option enabled, the following thread was identified
    as freeing 64 bytes instead of 8 bytes previously obtained and
    therefore causing an overlay:
    
    Native traceback:
    operator delete(void*)
    Java_com_ibm_ws390_tx_ControllerTransactionManagerSet_getSysplex
      IdNative
    SIDECARINVOKEREFLECTMETHOD
    JVM_InvokeMethod
    JVM_InvokeMethod
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0
    SIDECARINVOKEREFLECTMETHOD
    JVM_InvokeMethod
    JVM_InvokeMethod
    Java_sun_reflect_NativeMethodAccessorImpl_invoke0
    RUNCALLINMETHOD
    gpProtectedRunCallInMethod
    signalProtectAndRunGlue
    j9sig_protect
    gpCheckCallin
    callStaticVoidMethodA
    CPPtoJAVAUtilities::startServer()
    CORBA::ORB::BOA_init(int&,char**,char*)
    
    Java traceback:
    com/ibm/ws390/tx/ControllerTransactionManagerSet.
      getSysplexIdNative
    com/ibm/ws390/tx/ControllerTransactionManagerSet.getSysplexId
    com/ibm/ws/Transaction/JTS/TxIORInterceptor.<init>
    com/ibm/ws/Transaction/JTS/TxInterceptorInitializer.pre_init
    com/ibm/rmi/pi/InterceptorManager.runPreInit
    

Local fix

  • Apply level 7.0.0.21 or later
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM WebSphere Application       *
    *                 Server V8.0                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Controller Region terminates with       *
    *                      abend code 9C6 and reason code          *
    *                      00200001 during server startup.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The controller region (31 bit mode configured) terminates
    with abend code 9C6 (ABEND9C6) and reason code 00200001 during
    server startup.
    The issue was caused by code that incorrectly
    cleared 64 bytes as opposed to 64 bits of data prior
    to attempting to retrieve the system's sysplex id during
    server startup.
    Note that due to the nature of memory overlays the symptom
    can vary and can include 0C4 abends (ABEND0C4). However,
    when this issue was reported, the following was observed:
    The controller region SYSPRINT log shows:
    Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=S2
    Description: Log Boss/390 Error
    from filename: ./bborexit.cpp
    at line: 1111
    error message: BBOO0033W Processing for signal 'SIGABND'
    (18) with abend=009C6000 rsncode=00200001
    si_code='ABND_REAL'(170) si_errno=0 si_addr=00000000 ,
    in current thread (136090000000004E 006BEE88).
    Trace: xxxx/xx/xx xx:xx:xx.xxx xx t=xxxxxx c=UNK key=S2
    Description: Log Boss/390 Error
    from filename: ./bborexit.cpp
    at line: 1308
    error message: BBOO0034W Terminating the current
    thread (136090000000004E 006BEE88), REASON=C9C20009.
    The controller region dump shows the terminated thread
    performing the following task:
    TCB Address: xxxxxxxx
    Traceback:
    DSA      Entry       E  Offset  Statement   Load Mod
    1        BBOG_LogRequestTable::obtainLatch(int,char(&).8.)
    -3DB31A54              *PATHNAM
    2
    BBOG_FailureMonitor::processRecoveryLogRequest(bbogsrdd*)
    +00000256              *PATHNAM
    3        BBOG_FailureMonitor::processACRW(acrwObj&)
    +000000D6              *PATHNAM
    4
    ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
    +00000C3C              *PATHNAM
    5        ACR_ExecutionRoutine
    +0000020C              *PATHNAM
    6        CEEVROND    +000011F4              CEEPLPKA
    7        CEEOPCMM    +000009A2              CEEBINIT
    When when the abend is investigated an overlay of
    a heap pool 1 element is seen. The length of the overlay
    is 64 bytes and the content of the overlay is 0s; however, the
    good heap element prior to the overlaid element may contain
    data other than nulls if the element was reused.  An example
    of the overlay pattern is:
    5C00C4C9 E300F0F0 0070726F 70657274 | *.DIT.00...?.... |
    69657300 00000000 00000000 00000000 | ................ |
    00000001 00000001
    00000000 00000000 00000000 00000000 | ................ |
    00000000 00000000 00000000 00000000 | ................ |
    00000001
    

Problem conclusion

  • Code was added to correctly clear the appropriate amount of
    storage.
    
    APAR PM51888 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.21 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM51888

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-09

  • Closed date

    2011-12-15

  • Last modified date

    2012-02-22

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

    PM44349

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

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK74996

       UP12/01/18 P 1201

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022