Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Needs more information
Workspace WebSphere Liberty
Created by Guest
Created on Jan 26, 2026

Update z/OS Logging to support wildcards in message specification e.g. CWKK* or CWKK10%%

For automation we require certain error messages in z/OS Connect (A liberty application) to be routed to the system log. The current specification for hardCopyMessage and wtoMessage as part of the Configuration properties for logging on z/OS see https://www.ibm.com/docs/en/was-liberty/zos?topic=configuration-zoslogging does not support any wildcards. This is unfortunate as there are hundreds of information, warning and error messages that can be issued. A specific requirement for us relates to automatic server configuration checking during startup of z/os connect. To do this we would like to send current and future messages to the system log so automation can act on them if they are issued during startup. There are already more than 100 CWWKG* messages and coding a list this long is awkward. Also new messages may be added at any time so keeping this list up to date would be require further work.  The use of generics would make specification of the messages in server.xml a lot easier and allow us to code for new messages to be automatically sent to the system log if they match existing wildcards. This enhancement would also benefit any users of liberty servers on z/OS not just z/OS Connect users. Sugggested iimplementation support * as a wild card e.g. CWWKG*  and potentially % as a single character wild card e.g. CWWKG%%I

Idea priority Medium