IBM Z Software
This portal is to open public enhancement requests against IBM Z Software 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
There are a couple of ways this requirement could be achieved:
The first way this can be achieved is by using the binaryLogging feature. See this page for more details about binaryLogging https://www.ibm.com/docs/en/zosconnect/3.0?topic=problems-enabling-trace-in-zos-connect-ee#trace__logging_performance You must upgrade to at least V3.0.47 to use binaryLogging.
The fileSwitchTime option can be specified to set the hour of the day at which the server will close the current log file and create a new one. This configuration means that you can have one file per day and the old log files can then be archived for storage as required.
For example, specifying com.ibm.hpel.log.fileSwitchTime=23 will cause a new log file to be started at 23:00UTC every day. Full details of the configuration options can be found here https://www.ibm.com/docs/en/was-liberty/base?topic=logging-configuring-binary-in-liberty
The other way this can be achieved is to configured the regular logging to create multiple log and trace files. This is set using the maxFiles attribute on the logging element in server.xml. If this value is set to 10 then up to 10 files will be created. The active files are messages.log and trace.log. Once each of these files reach the maximum size as specified by maxFileSize then they will be saved with a timestamp and a new log will be created. Any file with a timestamp in it can then be safely moved elsewhere for archive purposes. This can be scripted and run automatically on a regular basis. You can find more detail about both parameters here: https://www.ibm.com/docs/en/was-liberty/base?topic=liberty-logging-trace