Tracing Managed File Transfer standalone loggers on Multiplatforms

The trace facility in Managed File Transfer is provided to help IBM Support diagnose your problems and issues. Various commands and properties control the behavior of this facility.

If we are asked to provide trace output to investigate an issue with a logger, use one of the following options, depending on whether it is possible for you to stop the logger for a short period of time.

If we are unsure which option to use, contact the IBM Support representative and they will advise you on the best way to collect trace for the issue that we are seeing.

Procedure

• If it is possible for you to stop a logger for a short period of time, collect a trace of the logger from startup. For more information, see Collecting a Managed File Transfer standalone logger trace from startup.
• If it is not possible for you to stop a logger, then collect a trace dynamically using the fteSetLoggerTraceLevel command. For more information, see Collecting a Managed File Transfer standalone logger trace dynamically.

• Collecting a Managed File Transfer standalone logger trace from startup
  Where it is possible for you to stop a logger for a short period of time, we should collect Managed File Transfer logger trace from startup.
• Collecting a Managed File Transfer standalone logger trace dynamically
  The fteSetLoggerTraceLevel command allows trace to be collected from a running logger. This can be very useful if IBM Support need to see a trace from a logger that cannot be stopped.

Parent topic: Tracing Managed File Transfer resources on Multiplatforms