Fixes are available
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4
APAR status
Closed as program error.
Error description
The following behaviors make it difficult or impossible to automate operations for Liberty based on the output to the z/OS master console, or from the job's log: 1) When using the zosLogging configuration in server.xml to route messages, specifying the wild card * character causes some messages to be issued twice. 2) The documentation for zosLogging does not describe which route codes are used when messages are routed using WTO 3) Message CWWKE0036I, which indicates that the server is stopped, cannot be routed to job log or the z/OS console 4) In some circumstances it is desirable to suppress all messages from going to the job log or z/OS console, and there is currently no way to over-ride the default behavior.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty for z/OS * **************************************************************** * PROBLEM DESCRIPTION: It is difficult to automate based on * * Liberty messages on z/OS * **************************************************************** * RECOMMENDATION: * **************************************************************** There are a number of challenges that the user will encounter when attempting to use automation on z/OS to manage the lifecycle of a Liberty server. When stopping the server, message CWWKE0036I indicates that the server has stopped, however this message cannot be routed to the z/OS console or joblog because the server has already unloaded the code that can route messages to the z/OS console. In other circumstances, customers may wish to redirect all messages to the z/OS console or joblog by using the wild card * character in the zosLogging configuration in server.xml. The message routing code will interpret the wild card character in addition to any other messages that are logged to the z/OS console by default, and the result is that some messages, including CWWKF0011I The server defaultServer is ready to run a smarter planet, are logged twice. For users who wish to disable all messages from being written to the z/OS console, there is no way to prevent the default set of messages from being written. Finally, the documentation for zosLogging is unclear on which routing codes are used by WTO to write messages to the z/OS console or to the job's log. This can make it difficult to write automation rules for a Liberty server.
Problem conclusion
Code was added to print message CWWKB0251I to WTO and hardcopy, indicating that the Liberty z/OS kernel extension has completed shutdown. This message may be used by automation to indicate that the Liberty server has stopped. Code was added to eliminate duplicate messages that were printed when the wild card * character is used in the zosLogging configuration. Attributes disableWtoMessages and disableHardcopyMessages were added to the zosLogging configuration. These attributes prevent the Liberty server from logging any message to WTO or hardcopy. The description of attributes wtoMessage and hardCopyMessage were updated to reflect the WTO route codes that are used to print messages, as well as the default set of messages that are printed. The fix for this APAR is currently targeted for inclusion in fix pack 18.0.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI96813
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-04-16
Closed date
2018-04-26
Last modified date
2018-04-26
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
LIBERTY PROF -
Fixed component ID
5655W6514
Applicable component levels
RCD0 PSY
UP
Document Information
Modified date:
04 May 2022