IBM Support

IT26410: With CHAD enabled a new SVRCONN channel results in AMQ9498: The MQCD structure supplied was not valid.

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 a new server connection channel needs to be created
    and Channel Auto Definition (CHAD) is enabled then queue manager
    errors are seen:
    
    AMQ9498: The MQCD structure supplied was not valid.
    
    EXPLANATION:
    The value of the 'MsgUserDataPtr' field has the value '(nil)'.
    This value is invalid for the operation requested.
    ACTION:
    Change the parameter and retry the operation.
    
    The amqrmppa trace shows
    
     ----------{ rrxValidateChannel
     -----------{  rrxError
         RetCode = 20009498,
    rc1 = 0, rc2 = 0, Comment1 = 'MsgUserDataPtr', Comment2 =
    '(nil)',
    Comment3= '', File=
    '/build/slot1/p800_P/src/lib/client/amqrcdua.c',
    Line= '390'
     -----------}! rrxError
    rc=rrcE_INVALID_MQCD FunctionTime=8
     ----------}!
    rrxValidateChannel rc=rrcE_INVALID_MQCD
    

Local fix

  • A workaround is to restart the queue manager with the -c option,
    i.e.
    
    strmqm -c QMGR
    
    This will recreate the SYSTEM.AUTO.SVRCONN channel without the
    incorrect MsgExit value.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who have redefined the SYSTEM.AUTO.SVRCONN channel and who
    have auto-defined channels (CHAD) enabled may be affected by
    this issue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The problem occurs when the SYSTEM.AUTO.SVRCONN channel is
    deleted and then redefined.
    
    The internal base definition for SVRCONN channels incorrectly
    include a value for MsgExit and this was exposed when the
    SYSTEM.AUTO.SVRCONN was redefined.
    
    Part of the procedure for creating an auto-defined SVRCONN
    channel is to validate the new channel definition.  This
    validation failed due to the unexpected value for MsgExit that
    had been copied from the redefined SYSTEM.AUTO.SVRCONN channel.
    

Problem conclusion

  • The code has been modified so that the base SVRCONN channel
    definition does not contain a value for the MsgExit field.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.12
    v9.0 LTS   9.0.0.7
    v9.1 CD    9.1.3
    v9.1 LTS   9.1.0.3
    
    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

    IT26410

  • Reported component name

    IBM MQ APPL M20

  • Reported component ID

    5725S1400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-09-25

  • Closed date

    2019-04-24

  • Last modified date

    2019-04-24

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

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

Fix information

  • Fixed component name

    IBM MQ APPL M20

  • Fixed component ID

    5725S1400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
24 April 2019