PowerExchange can dynamically allocate a set of alternative message log files for logging messages.
When alternative logging is configured, PowerExchange writes runtime messages from PowerExchange components, programs, and commands to a set of alternative log files that are used on a rotating basis, which can help prevent out-of-space conditions. When the current log file becomes full, PowerExchange switches to the next log file in a rotating manner. For example, if you configure alternative logging to write to five disk files, which is the default, when the fifth file reaches its maximum size threshold, it is closed and logging resumes by overwriting the first file.
PowerExchange dynamically allocates alternative log files if they do not exist.
PowerExchange continues to write initial startup messages to the primary PowerExchange message log file.
Alternative message logging has the following benefits:
You can control the size and number of alternative log files and the frequency with which PowerExchange flushes the log records to the file. Setting frequent flushes reduces latency in being able to view messages through the PWXUMSGS utility or direct browsing.
PowerExchange uses multiple files for logging messages. When the current log file becomes full, PowerExchange can switch to the next log file, thereby preventing out-of-space conditions.
After opening an alternative log file, PowerExchange buffers messages so that they can be written to a log file on disk at a specified interval. This buffering reduces the amount of open, close, and write activity on the file to improve performance and resource usage.
On z/OS, spool resources are minimized for long-running jobs.
On Windows, you can retrieve messages using the PUWXUMSG utility.