IBM Support

IT16856: MQ fails to read security group name from queue manager configuration file

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 creating a queue manager with the option "-a" with a
    domain group, the SecurityGroup information is added in qm.ini
    file as below:
    AccessMode:
       SecurityGroup=<Domain Name>\<Group Name>
       RemoveMQMAccess=FALSE
    
    However, the queue manager fails to start because it can't
    obtain correct security group information. From MQ trace, there
    are some incorrect characters added after group name.
    
    C:\Users\mqmuser>strmqm -x test
    AMQ7026: A principal or group name was invalid.
    
    00059B68 14:17:12.849159   4064.1           :       (03)----{
    xcsSetSecurityAtts
    ..
    00059DDC 14:17:12.854918   4064.1           :       (04)-----{
     xcsGetNTGroupSID
    00059DDD 14:17:12.854924   4064.1           :
    GroupId(abcd\mqmuser?)
    ..
    00059DE0 14:17:12.861334   4064.1           :       Unable to
    obtain SID, checking for local definition of abcd\mqmuser?.
    00059DE1 14:17:12.861345   4064.1           :       (05)------{
     xcsCheckLocalGroup
    00059DE2 14:17:12.861352   4064.1           :
    GroupId(abcd\mqmuser?)
    00059DE3 14:17:12.861924   4064.1           :       Local group
    abcd\mqmuser? does not exist.
    00059DE4 14:17:12.861945   4064.1           :       (05)------}!
    xcsCheckLocalGroup (rc=zrc_CSPRC_AUTH_NO_LOCAL_GROUP)
    00059DE5 14:17:12.861965   4064.1           :       (04)-----}!
    xcsGetNTGroupSID (rc=zrc_CSPRC_AUTH_NO_LOCAL_GROUP)
    00059DE6 14:17:12.861975   4064.1           :       (03)----}!
    xcsSetSecurityAtts (rc=lpiRC_CSPRC_UNKNOWN_ENTITY)
    
    The "?" character following the groupID is indicative of the
    issue. Depending on the local encoding/codepage a different
    unexpected character may appear in place of the "?".
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of MQ multi-instance queue managers on Windows with a
    domain group
    
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A coding error in the MQ queue manager caused an unexpected
    character to be added to the SecurityGroup while starting the
    queue manager. Addition of this extraneous character to the
    security group caused the observed failure while validating the
    group details, which in turn caused the failure to start the
    queue manager.
    

Problem conclusion

  • The MQ code has been updated such that the correct SecurityGroup
    name is used during the start of queue manager.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.2
    v9.0 LTS   9.0.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

    IT16856

  • 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

    2016-08-31

  • Closed date

    2016-11-30

  • Last modified date

    2017-06-01

  • 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 BASE M/P

  • Fixed component ID

    5724H7261

Applicable component levels

  • R900 PSY

       UP

[{"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:
01 June 2017