Collecting a Managed File Transfer for z/OS agent trace from startup

Collecting a Managed File Transfer for z/OS agent trace from startup

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

About this task

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

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

Procedure
If you are using:

Unix System Services (USS), see Collecting an agent trace from startup using USS.
JCL, see Collecting an agent trace from startup using JCL.

Collecting an agent trace from startup using USS
To collect a trace of a Managed File Transfer for z/OS agent that is being administered using Unix System Services (USS) from startup, you need to set various properties need in the agent.properties file for that agent before it is started.
Collecting an agent trace from startup using JCL
To collect a trace of a Managed File Transfer for z/OS agent that is being administered using JCL from startup, you need to set various properties need in the agent.properties file for that agent before it is started.
Parent topic: Tracing Managed File Transfer for z/OS agents