IBM Support

IT25614: MQ 9.0: AMQ8227 Channel not found error when issuing command to stop auto-defined CLUSSDR channel

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When using MQ 9.0 and issuing runmqsc command "stop channel"
    for an auto-defined clussdr channel, the following error is
    generated:
    AMQ8227 channel not found
    
    The runmqsc commmand "DISPLAY CHS" (to display channel status)
    shows that the clussdr channel is in running state.
    
    The problem happens when the environment variable is set while
    creating queue manager:
      MQSNOAUT=YES
    
    Because of this environment variable, the Authorization Service
    stanza is not created inside the file qm.ini.
    

Local fix

  • Recreate the queue manger without setting the environment
    variable:
      MQSNOAUT=YES
    If you have already created the environment variable, unset it:
    Windows:  set MQSNOAUT=
    Unix:     unset MQSNOAUT
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users that have created a queue manager with no authorization
    service by setting MQSNOAUT=YES before running crtmqm and
    configures the queue manager to be a member of a Queue Manager
    Cluster
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem occured because authorisation checking returned a
    success return code when no authorization service is available.
    Some cluster object lookup code relies on an
    MQRC_UNKNOWN_OBJECT_NAME return code  to be returned for local
    object checks, before it proceeds to look up the object (in this
    case a channel) in the cluster cache.
    

Problem conclusion

  • The problem is fixed by enabling an error to be returned during
    the authorization check in the code (which would typically
    return success when no authorization service is available) and
    handling the error code to perform checks and processing that
    would otherwise not be executed.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 LTS   9.0.0.6
    v9.1 CD    9.1.1
    v9.1 LTS   9.1.0.1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25614

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-06

  • Closed date

    2018-08-15

  • Last modified date

    2018-08-15

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

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

    PH01745

Fix information

  • Fixed component name

    IBM MQ BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

[{"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:
15 August 2018