Collecting a trace of a command using USS
To collect a trace of a Managed File Transfer for z/OS® command using Unix System Services (USS) carry out the following procedure.
Procedure
- Bring up a command prompt, and navigate to the BFG_PROD/bin directory.
- Run the
command:
./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.
Example
In this example, the fteListAgents command is traced, and the trace is written to the /u/fteuser directory:./fteListAgents -trace com.ibm.wmqfte=all -tracePath /u/fteuserIn 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 /tmp/IEEUJV.txt "//'SYS1.SAMPLIB(IEEUJV)'"
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.