Tracing Managed File Transfer commands on Multiplatforms

The trace facility in Managed File Transfer is provided to help IBM® Support diagnose your problems and issues. We can use this facility to trace commands.

About this task

Attention: Tracing a command only collects information about the processing done by the command. It does not trace any activity that an agent might perform while processing that command.

Procedure

1. Bring up a command prompt, and navigate to the MQ_INSTALLATION_PATH\bin directory.
2. Run the command:

   ./command_name -trace classes=level -tracePath directory_path command_arguments 

   command_name -trace classes=level -tracePath directory_path command_arguments 

   where
   • command_name is the name of the command to be traced.
   • classes=level is the trace level to use, and which classes to enable trace for. Unless otherwise specified by your IBM Support Representative, set this to com.ibm.wmqfte=all.
   • directory_path is the directory where the trace files will be written to.
   • command_arguments are the arguments that need to be passed to the command, for example, the name of the agent for the ftePingAgent command.

Results

The resultant trace files are written to the directory specified by the -tracePath parameter.

The trace files are called trace%PID%.txt.number, where:

• %PID% is the process identifier for the command.
• number is a sequence number for the trace file. Typically, the trace information generated by a command is contained within a single trace file that has a sequence number of 0.

  However, it is possible that a command will generate a lot of trace information. In this situation, the trace will be written to multiple files. The current trace file has a sequence number of 0, the next oldest trace file has a sequence number of 1, and so on.

Trace output for commands are written to a maximum of five wrapping trace files. The maximum size of each trace file is 20MB.Note: If the user running the command does not have permission to write to the directory specified by the -tracePath parameter, the trace output is written to standard error.

Example

In this example, the fteListAgents command is traced, and the trace is written to the C:\trace directory:

fteListAgents -trace com.ibm.wmqfte=all -tracePath C:\trace  

In this example, the fteCreateTransfer command is traced, and the trace is written to the /tmp directory:

fteCreateTransfer -trace com.ibm.wmqfte=all -tracePath /tmp -t text -sa AGENT1 
-da AGENT2 -df /import/transferredfile.txt /export/originalfile.txt

The trace file written to /tmp only contains information about the processing performed by the fteCreateTransfer command, such as, how the command builds the transfer request message that is sent to the agent, and how long it waits for the agent to send back an acknowledgment indicating that it has received the request. The trace file does not contain any information about the transfer itself.