IBM Support

PI68897: CHIN ABEND 0C4-00000011 CSQXADPM WITH CSQSNAP WITH XFFSRSTMVSASYNCCONSUMERTHREAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CHIN abends and goes down with the following error messages:
    
    ----------------------------------------------------------------
    +CSQX053E +CSQ1 CSQXFFST Error information recorded in CSQSNAP
              data set
    +CSQX112E +CSQ1 CSQXDISP Dispatcher process error, TCB=009C46D8
              reason=0C4000-00000011
    CSQY291E CSQXDMPS SDUMPX FAILED, RC=00000208,CSQ1,ABN=
             5C6-00E70054, LOC=CSQXADPM.CSQXADPM
    IEA794I SVC DUMP HAS CAPTURED:  680
    DUMPID=059 REQUESTED BY JOB (MQT2CHIN)
    +CSQX209E +CSQ1 CSQXRESP Connection unexpectedly terminated,
           DUMP TITLE=CSQ1,ABN= 0C4-00000011
           M=CSQXDISP,LOC=CSQXADPM.????????
           channel UYG.ESB.TO.MQ
           connection <connection> (<ipaddr>)
     (queue manager CSQ1)
     TRPTYPE=TCP RC=00000000
    ----------------------------------------------------------------
    
    CSQSNAP shows eyecatchers:
    
    ----------------------------------------------------------------
    *X...XFFSrstMVSAsyncConsumerThrea*
    *d.......MOVR.........$&#162;&X...XINS*
    *................................*
    
    and
    
    *                        ....Inva*
    *lid aCon state..ACNV............*
    *......................K.........*
    *................................*
    *............... .. ........... .*
    *.. ...{\............            *
    ----------------------------------------------------------------
    
    The initial abend, the 0C4 in CSQXADPM, has occurred as the
    cciCONV control block at 2B34FBD0 has been released by
    ccxFreeAllMpxConvMem although it has subsequently been
    referenced.
    .
    Additional keywords:
    CSQX053E CSQX112E CSQX209E
    rstMVSAsyncConsumerThread invalid acon state acnv
    ABEND0C4 ABENDS0C4 S0C4 S00C4
    

Local fix

  • No Local Fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of IBM MQ for z/OS Version 9 Release 0             *
    * Modification 0.                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using conversation sharing (SHARECNV>0) with svrconn    *
    * channels, various errors and abends can occur including:     *
    *                                                              *
    *                                                              *
    * "+CSQX112E +xxxx CSQXDISP Dispatcher process error,          *
    * TCB=008CB510 reason=5C6000-00E70056"                         *
    *                                                              *
    * "+CSQX113E +xxxx CSQXDISP Dispatcher ended abnormally,       *
    * TCB=008CB510 reason=5C6000-00E70054"                         *
    *                                                              *
    * CSQX053E reporting an FFST in the CSQSNAP DD. The FFST is    *
    * written by rstMVSAsyncConsumerThread with reason "Invalid    *
    * aCon state"                                                  *
    *                                                              *
    * Abends 0C4, 0C6, 102 or 202 in module CSQXACNO               *
    *                                                              *
    * Abend 0C4 in module CSQXADPM                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * none                                                         *
    ****************************************************************
    When a conversation ends, any handles associated with the
    conversation are deregistered with the queue manager, preventing
    them being posted, and the handle storage and conversation
    storage is freed.
    In rare cases, the handle was already posted when the
    conversation was ended, but the post had not yet been processed
    by CSQXACNO.
    
    Due to inadequate serialisation between CSQXACNO and the ending
    conversation, this led to CSQXACNO referencing the handle at
    unexpected times, or after the handle storage had been freed.
    
    Depending on exactly when CSQXACNO processed the post, and the
    state of the handle and conversation storage at that time, a
    variety of abends can occur.
    

Problem conclusion

  • CSQXACNO and CSQXRSTM are updated to serialise processing more
    effectively when conversations end, preventing CSQXACNO
    accessing handles that are no longer valid.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI68897

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-09

  • Closed date

    2016-10-13

  • Last modified date

    2017-05-19

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

    PI55507

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

    UI41635

Modules/Macros

  • CSQXACNO CSQXRSTM
    

Fix information

  • Fixed component name

    MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI41635

       UP17/01/10 P F701

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 May 2017