IBM Support

PI97541: IBM MQ V800 CSQX599E generated after CSQX514E is confusing

A fix is available


You can track all active APARs for this component.


APAR status

  • Closed as program error.

Error description

  • In a cluster environment, receipt of message CSQX599E, after
    CSQX514E is confusing. This occurrence is related to a timing
    window seen by Change Team when a START CHANNEL has not yet been
    scheduled while its status is rrXCS_NO_STATUS. Meanwhile the
    channel is trigger started (via CSQMPCHS) so that, by the time
    the START command is actioned the start by trigger is already
    done, resulting in CSQX514E. Processing for the Qmgr and CHINIT
    continue normally however output of this message may be

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 8       *
    *                 Release 0 Modification 0                     *
    * PROBLEM DESCRIPTION: When a cluster sender channel is        *
    *                      started by a command, and messages are  *
    *                      on the cluster transmit queue, messages *
    *                      CSQX514E and CSQX599E may be seen       *
    *                      stating the channel has stopped         *
    *                      abnormally. However the channel remains *
    *                      active and does not stop.               *
    The start command sets the channel status in the cluster cache
    to INACTIVE prior to scheduling the start. This provides a small
    window for another start via triggering to occur if messages are
    on the cluster transmit queue at this time. The trigger start
    completes first, thus the manual start subsequently fails with
    message CSQX514E since the channel is already started. This is
    followed by abnormal end message CSQX599E.

Problem conclusion

  • Code has been changed so that in this particular case the
    trigger start will not occur, and the manual start completes

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    IBM MQ Z/OS V8

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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

    IBM MQ Z/OS V8

  • Fixed component ID


Applicable component levels

  • R000 PSY UI56618

       UP18/07/25 P F807

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":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 August 2018