IBM Support

PI18400: WMQ SERVER CHANNEL GOES INTO A STOPPED STATE IF IT SPECIFIES CONNAME(), SHORTRTY(0) AND LONGRTY(0)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WMQ Server Channel goes into a STOPPED state if
    it specifies CONNAME(), SHORTRTY(0) and LONGRTY(0).
    .
    You will see a "CSQX599E" error message in the
    CHIN log, if you alter the channel definition
    and specify CONNAME(), SHORTRTY(0) and LONGRTY(0)
    .
    +CSQX599E MQH1 CSQXRESP Channel <channel.name> ended
    abnormally.
    .
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ Version 7          *
    *                 Release 0 Modification 1 and                 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a Server (SVR) - Requester (RQSTR)   *
    *                      channel pair with the server configured *
    *                      with SHORTRTY(0) and LONGRTY(0) counts  *
    *                      and CONNAME('') then the server state   *
    *                      is changed to STOPPED when the          *
    *                      requester stops the channel or there is *
    *                      a network error that terminates the     *
    *                      channel.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a SVR-RQSTR channel pair is stopped by the network or by
    RQSTR channel the SVR channel goes in STOPPED state preventing
    the channel to be started again by the RQSTR. The channel has
    to be manually started in the SVR side.
    
    This problem affects SVR channels that do not have a CONNAME
    defined and zero short/long retry counts.
    

Problem conclusion

  • rriWriteCompMsg in CSQXRMSS has been changed to avoid disabling
    server channels configured with zero retry counts allowing the
    channel to change to INACTIVE state.
    010Y
    100Y
    CSQXRMSS
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI18400

  • 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

    2014-05-21

  • Closed date

    2014-07-21

  • Last modified date

    2014-09-03

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

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

    UI19790 UI19791

Modules/Macros

  • CSQXRMSS
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UI19790

       UP14/08/30 P F408

  • R100 PSY UI19791

       UP14/08/30 P F408

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:
03 September 2014