IBM Support

PM73063: USERNAME NOT WRITTEN TO AUDIT-MS-COMPOUND.LOG FOR INVALID LOGON

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PROBMLEM DETAILS  :
    
     When a user fails to login to the MVS/VE console, the
    following message
    are shown in audit-ms-Compound.log.
    Juding from the documentation, username would be shown in
    front of
    the error message. But there is no username in the message.
    
     The customer wants to record the login success and login
    failure to
    the log file but username is not available in the
    audit-ms-Compound.log now. Need to show username in the log for
    all logon failures to the MS/VE.
    

Local fix

  • n/a
    

Problem summary

  • USERS AFFECTED: users with a failed login
    
    PROBLEM DESCRIPTION: If user tries to login with wrong
    credentials then username is not printed in the
    audit-ms-Compound.log
    
    RECOMMENDATION: Apply the fix 7103 ifix4
    

Problem conclusion

  • Username was not passed in the argument for
    the failed messages. Fixed the code.
    
    The fix for this APAR is included in 7.1.0.3 Ifix4
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM73063

  • Reported component name

    TCAM AD MAN SER

  • Reported component ID

    5724Y92MS

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-17

  • Closed date

    2013-01-29

  • Last modified date

    2013-01-29

  • 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

    TCAM AD MAN SER

  • Fixed component ID

    5724Y92MS

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDTFJ","label":"Tivoli Composite Application Manager for Application Diagnostics"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 July 2021