IBM Support

PH08669: WMQ SERVER CHANNEL CONFIGURED ON Z/OS WILL GO TO A STOPPED STATEWHEN REFRESH SECURITY TYPE(SSL) IS ISSUED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Change Team finds when a SERVER channel is defined with SHORTRTY
    and LONGRTY of 0 while specifying a blank CONNAME, this channel
    can be terminated after REFRESH SECURITY TYPE(SSL) is executed.
    The subsequent restart process will attempt to start the SERVER
    channel as if it is fully qualified. This start later fails
    as the blank CONNAME can not be resolved, placing the channel
    into a STOPPED state. Further processing then depends on if the
    channel is defined with a non-zero retry counter. For SERVER
    channels defined with a zero retry no further attempts are made
    to start the channel and it is left in the STOPPED/DISABLED
    state. If the retry value is non-zero then the first retry is
    immediately triggered. This variant of retry does not attempt to
    perform a DNS lookup as it correctly recognizes that the
    CONNAME is blank and is treated as an operator START CHANNEL.
    This means SERVER channels without a CONNAME are incorrectly
    disabled by REFRESH SECURITY TYPE(SSL).
    

Local fix

  • Configure the channel with SHORTRTY(1)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0 and Version 9       *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: SERVER channels without a CONNAME are   *
    *                      incorrectly disabled by REFRESH         *
    *                      SECURITY TYPE(SSL).                     *
    ****************************************************************
    If a SERVER channel is defined without a CONNAME then when a
    SECURITY REFRESH TYPE(SSL) command is issued the SERVER channel
    goes into a STOPPED(DIABLED) state due to incorrect handling of
    SERVER channels during a security refresh.
    

Problem conclusion

  • SERVER channels without a CONNAME defined will no longer attempt
    to restart after a SECURITY REFRESH TYPE(SSL) and will instead
    be restarted when the REQUESTER channel issues a START command.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08669

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-18

  • Closed date

    2019-03-18

  • Last modified date

    2019-05-02

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

    PI93044

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

    UI61937 UI61938

Modules/Macros

  • CSQXRMRS
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI61937

       UP19/04/11 P F904

  • R100 PSY UI61938

       UP19/04/11 P F904

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

Document Information

Modified date:
02 May 2019