IBM Support

PM78268: WMQ STOP CHINIT COMMAND ISSUED BUT CHIN DOES NOT COMPLETE SHUTDOWN. SHUTDOWN HANG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Shutdown hang of channel initiator.
    You issued the STOP CHINIT command but the CHIN
    does not shutdown / terminate.
    !CSQ1 CSQMTCHI  STOP CHINIT COMMAND ACCEPTED
    You had to CANCEL the CHIN to terminate the task.
    CSQM137I !CSQ1 CSQMTCHI  STOP CHINIT COMMAND ACCEPTED
    PSMODE is set to ENABLED.
    .
    CHINIT trace shows the main pubsub daemon task is looping
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: The channel initiator does not end      *
    *                      after STOP CHINIT is issued.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The main pubsub daemon task loops browses messages from
    SYSTEM.BROKER.CONTROL.QUEUE. If no messages are available after
    10s, it performs a health check on any other daemon tasks,
    before reissuing the browse.
    When STOP CHINIT is issued, the supervisor calls rivStopPSDaemon
    which cancels the getwait in fdiBrowseNext, causing the daemon
    task to break out of the loop and end.
    However, if the task was not in a getwait (for example, it
    was performing the health check) when rivStopPSDaemon runs, it
    does not adequately check if it should stop, and continues to
    loop, preventing the chinit from stopping, unless the queue
    manager is also stopped.
    

Problem conclusion

  • fdiBrowseNext will perform an additional check to determine
    whether it has been requested to stop, preventing the reported
    shutdown hang from occurring.
    010Y
    100Y
    CMQXFDIA
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM78268

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-12-03

  • Closed date

    2012-12-21

  • Last modified date

    2013-03-04

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

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

    UK90566 UK90567

Modules/Macros

  • CMQXFDIA
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UK90566

       UP13/02/05 P F302

  • R100 PSY UK90567

       UP13/02/05 P F302

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 March 2013