Collecting a Managed File Transfer for z/OS standalone database logger trace from startup

Where it is possible for you to stop a logger for a short period of time, we should collect IBM MQ Managed File Transfer logger trace from startup.

The way to collect the trace depends on whether the logger is being administered using UNIX System Services (USS) or JCL.

If we are unsure which of the following options 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

• UNIX System Services (USS), see Collecting a standalone database logger trace from startup using USS.
• JCL, see Collecting a standalone database logger trace from startup using JCL.

• Collecting a standalone database logger trace from startup using USS
  To collect a trace of a Managed File Transfer for z/OS logger that is being administered using Unix System Services (USS) from startup, set various properties in the logger.properties file for that logger before it is started.
• Collecting a standalone database logger trace from startup using JCL
  To collect a trace of a Managed File Transfer for z/OS logger that is being administered using JCL from startup, set various properties in the logger.properties file for that logger before it is started.

Parent topic: Tracing Managed File Transfer for z/OS standalone database loggers