IBM Support

PK61983: MQ QUIESCE HANGS AFTER MIGRATING TO CICS 3.2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • After a new start of CICS, if MQ is quiesced while leaving CICS
up, the first MQ quiesce will work. But after MQ is brought back
up and CICS reconnects, a second quiesce of MQ will hang. MQ has
to be forced down.
.
The cause of the hang appears to be that there is a thread still
associated with the CKAM task. When MQ is first quiesced, CKAM
remains to retry the connection. During reconnect processing,
DFHMQCON issues several MQ requests to obtain the MQ release
level. These MQ requests are issued under the CKAM task and
cause CKAM to acquire a thread. But because CKAM doesn't
terminate, but instead waits for MQ to become available, the
thread is not terminated either. This causes the second quiesce
of MQ to hang because there is still an active thread for CKAM.

Local fix

  • Additional Symptom(s) Search Keyword(s):
KIXREVrbd

Problem summary

  • ****************************************************************
* USERS AFFECTED: All.                                         *
****************************************************************
* PROBLEM DESCRIPTION: Quiesce of WMQ may hang.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A CICS region is connected to WMQ and WMQ is quiesced. WMQ is
then restarted and quiesced again, on this second quiesce the
WMQ attachment does not complete its quiesce.

Problem conclusion

  • 



Temporary fix


    

  • 



Comments


    

  • This APAR is being closed FIN with concurrence from the
submitting customer.  This means that a fix to this APAR is
expected to be delivered from IBM in a release which is being
developed at the time that the APAR was closed.
The latest release of the product to exit development at the
time this APAR was closed was:
  CICS Transaction Server for z/OS V3.2.
EUR22287  EUR 22287

    



APAR Information




    

  • APAR number
    PK61983
    • 

  • Reported component name
    CICSTS V3 Z/OS
    • 

  • Reported component ID
    5655M1500
    • 

  • Reported release
    500
    • 

  • Status
    CLOSED  FIN
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2008-02-29
    • 

  • Closed date
    2008-09-30
    • 

  • Last modified date
    2008-09-30
    • 





    

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

    • 

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

    • 



Fix information


    



Applicable component levels


    

  • R500  PSN
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            30 September 2008
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback