IBM Support

PM84391: STOP CHANNEL COMMAND ABNORMALLY TERMINATED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem seems same problem as FIN closed apar PQ55634.
    When we issued STOP CHL() for the RETRYING status channel,
    "CSQX533I Channel is already stopped" was issued, and STOP CHL()
    abnormally terminated, it follows that the channel is still
    RETRYING status.
    Looks like this is timing problem and very intermittent.
    If we issue STOP CHL() again, the command was executed normally.
    

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: When a channel is in retry, a STOP      *
    *                      CHANNEL command may return a CSQX533I   *
    *                      message and at V701 the channel may     *
    *                      not stop but continue to retry.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a channel goes into retry, the status changes through
    Initializing, Starting, Binding. If an operator enters the STOP
    CHANNEL command at the precise moment that the channel is
    Initializing or Binding, then the message CSQX533I may be
    returned - indicating that the channel is already stopped. In
    such circumstances, in the case of a Version 7.0.1 queue
    manager, the channel may continue to retry and a STOP CHANNEL
    may have to be re-issued.
    
    The problem is that, in the STOP CHANNEL code, the Initializing
    and Binding states are not recognized as active channel states.
    In addition, for a Version 7.0.1 queue manager, due to an error
    in logic in the channel restart code, the channel status of
    Stopped, set by the stop command, is being overwritten.
    

Problem conclusion

  • The code has been changed to recognize Initializing and Binding
    as active states of the channel and to honour the STOP CHANNEL
    command.
    010Y
    100Y
    CSQXRCMS
    CSQXRCSI
    

Temporary fix

Comments

  • ×**** PE14/01/30 FIX IN ERROR. SEE APAR PI06816  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PM84391

  • 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

    2013-03-07

  • Closed date

    2013-06-27

  • Last modified date

    2014-02-07

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

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

    UK95529 UK95530

Modules/Macros

  • CSQXRCMS CSQXRCSI
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UK95529

       UP13/08/23 P F308

  • R100 PSY UK95530

       UP13/08/23 P F308

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:
07 February 2014