IBM Support

PH39946: Liberty logging hideMessage= parameter should also stop messages being written to messageLogDD=MSGLOG

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 current capability provided by Liberty logging
    hideMessage= allows a message being written to messages.log
    file to be suppressed and written to trace.log file instead.
    When zoslogging messageLogDD=MSGLOG is in use, any messages
    written to messages.log are also written to DD MSGLOG.
    Coding hideMessage= stops the message being written to
    message.log but the message is still written to DD MSGLOG.
    If it is suppressed from message.log it should also be
    suppressed from DD MSGLOG.

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    * PROBLEM DESCRIPTION: Liberty messages specified on           *
    *                      hideMessage= are being written to the   *
    *                      DD specified on messageLogDD=           *
    * RECOMMENDATION:                                              *
    Liberty messages specified on hideMessage= are being written to
    the DD specified on messageLogDD= because the
    message log log handler does not check messages against what was
    specified on hideMessage=.
    The following requests that CWWKF0012I be hidden.
    <logging hideMessage="CWWKF0012I" />

Problem conclusion

  • Updated the message log, hardcopy and WTO log handlers to not
    write messages specified on hideMessage=.
    The fix for this APAR is currently targeted for inclusion in fix
    pack  Please refer to the Recommended Updates page for
    delivery information:

Temporary fix


APAR Information

  • APAR number


  • Reported component name


  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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


  • Fixed component ID


Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"CD0"}]

Document Information

Modified date:
26 August 2021