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.

To collect a trace from startup, complete the following steps.

Procedure

1. Locate the logger.properties file for the logger that needs to be traced. The logger.properties file can be found in the BFG_DATA/mqft/config/coordination_qmgr_name/loggers/logger_name directory.
2. Edit the file and add entries for the following properties:
   • trace=trace specification

     The trace property determines the internal classes and packages that are to be traced. Unless otherwise specified by the IBM Support representative, set this property to the value com.ibm.wmqfte=all.

   • traceFiles=number of trace files to use
   • traceSize=size of each trace file, in MB

     The traceFiles and traceSize properties are used to control the amount of trace data that is collected. We should set these properties to large values, to collect as much trace data as possible.

   For example, to collect 1GB of wrapping trace using the trace specification com.ibm.wmqfte=all, add the following lines to the logger.properties file:

   trace=com.ibm.wmqfte=all
   traceFiles=5
   traceSize=200
   

   This results in the logger writing trace data to a maximum of 5 files, where each file has a size of 200MB.

   For more information on these logger properties, see The MFT logger.properties file.

3. Locate the data set containing the JCL for the logger that needs to be traced.
4. Submit the BFGLGSP member within the data set to stop the logger.
5. Restart the logger, by submitting the BFGLGST member in the data set.
6. Reproduce the issue.
7. Submit the BFGLGSP member in the data set to stop the logger again.
8. Edit the logger.properties file for the logger, and remove the entries for the trace, traceFiles, and traceSize properties that you added in step 2. This ensures that trace is not enabled the next time you restart the logger.

Results