You can remove entries from the transaction partner log
file. To do this, set the REMOVE_PARTNER_LOG_ENTRY custom property
for the transaction service on the server that owns the partner log.
About this task
As part of the transaction recovery process, the
partner
log is checked to establish which resources are needed. If you want
to remove certain entries from the partner log, such as a resource
that no longer exists, set this custom property on the application
server that owns the transaction partner log containing the entries
you want to remove.
The REMOVE_PARTNER_LOG_ENTRY custom property
is effective only when both of the following situations apply.
- The
application server is started in recovery mode.
- The application
server has no transactions that currently require
recovery. You can establish this by checking the SystemOut.log file.
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.