IBM Support

IT39225: The MQ Appliance usermodify command does not an report an error message for a non-existent user and generates FDCs

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 running usermodify command against a non-existent user to
    change password the following failure data capture (FDC) records
    are generated and no error message is reported to the user in
    the IBM MQ Appliance.
    
    Product Long Name :- IBM MQ Appliance
    Probe Id          :- MQ000003
    Program Name      :- dp_usermanager
    Comment1          :- Failed to execute 'chpasswd' command
    Comment2          :- chpasswd: line 1: user 'TEST' does not
    exist
     chpasswd:
        error detected, changes ignored
    
    MQM Function Stack
    xcsFFST
    
    Product Long Name :- IBM MQ Appliance
    Probe Id          :- DP059010
    Component         :- dpcMQUser
    Arith1            :- 101 (0x65)
    Comment1          :- Failed to execute 'dp_usermanager' command
    
    MQM Function Stack
    CLI
    dpcCmd_userModify
    dpcMQUser
    xcsFFST
    
    
    mqa(mqcli)# usermodify -u TEST -p "newpassword"
    mqa(mqcli)#
    
    Expected result:
    mqa(mqcli)# usermodify -u TEST -p "newpassword"
    AMQ6677E: The user modify command references an object that is
    not known.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users running usermodify command in MQ appliance running in MQ
    version 9.2.0.4 or 9.2.4.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A defect in error handling when modifying the user caused
    unexpected FDC records and also failures in reporting error
    message to the user if the command is executed against a
    non-existent user.
    
    This issue was introduced due to a logic error in the code
    change for APAR IT38979.
    

Problem conclusion

  • MQ code has been modified to prevent the unexpected FDC records
    and also to report an error to the user if the command is
    executed against a non-existent user.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.5
    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

    IT39225

  • Reported component name

    MQ APPL M2002 V

  • Reported component ID

    5737H4701

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-11-28

  • Closed date

    2021-12-21

  • Last modified date

    2022-01-05

  • 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":"920"}]

Document Information

Modified date:
06 January 2022