IBM Support

PI79179: CSQX514E ERROR OCCURS WHEN TRYING TO START CHANNEL WHILE PREVIOUS INSTANCE OF THE CHANNEL IS TERMINATING.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After migrating to MQ v8, the
    SYSTEM.CLUSTER.TRANSMISSION.QUEUE (SCTQ)
    curdepth does not trigger the CLUSSDR
    (Cluster-Sender Channel) to automatically
    start until there is manual start done
    on the channel.
    In the CHIN log, there is CSQX514E error
    message stating that the channel is
    in already active.
    .
    +CSQX514E SSID CSQXRCTL Channel <Cluster-Sender
    Channel> is active on SSID.
    .
    The problem occurs due to a timing situation
    where the previous instance of the channel
    is still in the process of terminating and
    has not yet got as far as deleting the
    connection tag for the channel
    (CSQMCRC1 invoked by CSQMCALH) when a new
    instance of the channel is started and
    rriRegisterChannelName tries to add the
    conection tag for the channel.
    However, as there is still a connection tag
    with the same name, the CSQX514E occurs.
    This connection
    tag processing has been added at MQ V8, hence
    the problem is seen after migrating to the new
    release.
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • Set DISCINT(0) on the CLUSRCVR.  That value will be
    propagated to the auto-defined CLUSSDR.  This will avoid the
    timing problem during disconnect processing.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of IBM MQ for z/OS Version 9 Release 0             *
    * Modification 0.                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Cluster sender channels may not start correctly and CSQX514E *
    * may be seen, if the channel is started within a small period *
    * of time since the channel stopped.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the cluster sender channel is stopped, the related state is
    cleared and the status of the channel is changed to closing
    (rrxCS_CLOSING). However if the channel is started again within
    a short time period, during the start, the processing may still
    find a connection tag for the channel, from the previous running
    state of the channel. When this is detected, the start does not
    complete for the channel and message CSQX514E is output.
    

Problem conclusion

  • Stop channel processing for cluster sender channels has been
    altered, to ensure connection tags are cleaned up prior to
    setting the channels state to allow another start.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI79179

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-31

  • Closed date

    2017-04-20

  • Last modified date

    2017-06-02

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

    PI78041

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

    UI46577

Modules/Macros

  • CSQXRMSS none
    

Fix information

  • Fixed component name

    MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI46577

       UP17/05/19 P F705

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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 June 2017