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

Where it is not possible for you to stop a logger for a short period of time, we should collect Managed File Transfer for z/OS logger trace dynamically.

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 dynamically using USS.
• JCL, see Collecting a standalone database logger trace dynamically using JCL.

• Collecting a standalone database logger trace dynamically using USS
  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.
• Collecting a standalone database logger trace dynamically using JCL
  We can use the BFGLGTC member within the dataset containing the JCL, for the logger that needs to be traced, to collect trace from a running Managed File Transfer for z/OS 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 for z/OS standalone database loggers