Enabling to specify wild card for hardCopyMessage and/or wtoMessage elements in zosLogging property

Backgrounds

The customer is migrating from WAS for z/OS traditional to WAS for z/OS Liberty. During the migration, many incompatibilities have been identified between the two products. We understand that WAS for z/OS traditional and WAS for z/OS Liberty are different products; however, IBM recommends migration to WAS for z/OS Liberty even though some mandatory functions available in WAS for z/OS traditional are missing in WAS for z/OS Liberty. From the customer's perspective, this is a functional regression. This Idea has been raised based on one of these incompatibilities.

Problem

Customer monitoring error/warning/critical messages which are issued by WebSphere traditional and handle the situation by automated software. This is very basic and important operation for mission critical online system. In case of WAS for z/OS traditional, customer monitor all messages whose IDs ended with "A", "S", "E", or "W". On the other hand, WAS for z/OS Liberty basically doesn’t issue any messages to SYSLOG, hence the messages are needed to be specified in hardCopyMessage element or wtoMessage element in zosLogging property to monitor them by automation products. However, specifying all messages which customer want to monitor in sever.xml is not realistic, because there are many messages to be monitored.

Customer Request
Please allow us to specify wild card in hardCopyMessage element and wtoMessage element for zosLogging property, such as CWWKE????E, *S, and so on, so forth.
This is mandatory for monitoring error/critical messages under mission critical online system.