IBM Support

IT38544: The MQ WebConsole only edits the first CHLAUTH records when multiple records exist for same 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 you have more than one CHLAUTH record defined for the same
    channel, and you click on the edit button via MQ Console on
    either of the defined records, it will display the details for
    the first record defined.
    
    For example, if the following records are created via runmqsc:
    
    DEFINE CHANNEL(CHANNEL.NAME) CHLTYPE(SVRCONN)
    SET CHLAUTH (CHANNEL.NAME) TYPE(ADDRESSMAP) ADDRESS('1.2.3.0')
    USERSRC(CHANNEL)
    SET CHLAUTH (CHANNEL.NAME) TYPE(ADDRESSMAP) ADDRESS('1.2.3.4')
    USERSRC(CHANNEL)
    SET CHLAUTH (CHANNEL.NAME) TYPE(ADDRESSMAP) ADDRESS('1.2.3.5')
    USERSRC(CHANNEL)
    
    WHhen you do the following via the MQ Console:
    
    Click on Manage Your queue managers
    Click on QMgrName
    Click on View Configuration
    Click on Security tab
    Click on Channel authentication
    
    A list with all defined CHLAUTH records is shown (including the
    3 that were defined earlier). However, if you click on the edit
    button on either one, all 3 of them shows the IP address of the
    first CHLAUTH record that was defined, in this case, the one
    for ADDRESS 1.2.3.0.
    

Local fix

  • Use runmqsc to edit the CHALUTH records instead of the MQ
    Console.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This affects users of IBM MQ WebConsole
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the WebConsole attempt to edit Channel authentication, the
    WebConsole will only look to edit the first one if there are
    multiple records that have been created for same channel.  This
    is due to the method used to generate an ID for each CHLAUTH
    entry, it is passed the CHLAUTH name.
    

Problem conclusion

  • The code has been updated to a method that will generate a
    unique ID for each CHLAUTH record and allow updating of the
    correct CHLAUTH record.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.x CD    9.2.4
    
    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

    IT38544

  • Reported component name

    MQ APPL M2002 V

  • Reported component ID

    5737H4701

  • Reported release

    923

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-29

  • Closed date

    2021-10-19

  • Last modified date

    2021-10-19

  • 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

    MQ APPL M2002 V

  • Fixed component ID

    5737H4701

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS5K6E","label":"IBM MQ Appliance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"923"}]

Document Information

Modified date:
20 October 2021