IBM Support

IT37969: The "ValidateAuth= No" qm.ini tuning parameter is not honored when AMQERR01.LOG is rolled over 

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

  • The attribute "ValidateAuth" was set to "No" in the Filesystem
    stanza of the qm.ini file e.g. :
    
      Filesystem:
          ValidateAuth= No
    
    and the permissions of the queue manager log files were changed.
     The ValidateAuth
    attribute should have ensured that the permissions of log files
    would be unaltered when the
    queue manager rolled the logs over, but in fact the permissions
    of AMQERR01.LOG
    changed unexpectedly on rollover.
    

Local fix

  • if  we "export AMQ_WRITEMSG=NORENAMEAMQERR01"  , Issue can be
    avoided.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All Users who have set
    ValidateAuth=No in the qm.ini file.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When logs rolled over and new AMQERR01.LOG file was created, a
    defect in the MQ code meant that the file permissions were not
    modified to match those of the old file.
    

Problem conclusion

  • The IBM MQ code has been modified so that the error log file
    permissions are retained when a new log file is created.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.12
    v9.2 LTS   9.2.0.6
    v9.x CD    9.3.0.0
    
    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

    IT37969

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-08-11

  • Closed date

    2022-03-11

  • Last modified date

    2022-04-13

  • 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 MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
14 April 2022