It is possible to reduce the sizes of the log file and
store files in the configuration. However, such reduction is only
possible when certain conditions are met.
About this task
Reducing the file sizes can be difficult in practice due
to the following reasons:
- It is not possible to shrink the files down below the amount of
space that their contents currently consume.
- There is no support for compaction of the contents of the permanent
store file and temporary store file so fragmentation might keep these
store files artificially large. As such, when the values of the file
sizes in the configuration are reduced and the messaging engine restarted,
it might not be possible to change the sizes of the files to the required
values.
When this situation occurs, the messaging engine emits warning
messages to
SystemOut.log and continues to use the
existing values. It attempts to apply the configuration changes repeatedly
each time it starts until it succeeds.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
Problems
might also arise when the file store file sizes are set too small.