fteSetLoggerTraceLevel (modify current trace level for a logger)
Use the fteSetLoggerTraceLevel command to modify the current trace level for a Managed File Transfer logger dynamically.
Purpose
Use this command to switch logger trace on and off or change the level of logger trace that is set. When you use the fteSetLoggerTraceLevel command, you do not have to shut down and restart a logger to modify the trace level. The trace files that are produced are located in MQ_DATA_PATH/mqft/logs/coordination_qmgr_name/loggers/logger_name/logs/trace%PID%/trace%PID%.txt, where %PID% is the process ID for the logger instance.
The fteSetLoggerTraceLevel command also writes a trace for the logger process controller. The trace files that are produced are located in MQ_DATA_PATH/mqft/logs/coordination_qmgr_name/loggers/logger_name/logs/pctrace%PID%/pctrace%PID%.txt, where %PID% is the process ID for the logger instance.
The command can also be used to cause the logger process to generate a Javacore. The logger generates a Javacore file in the following directory: MQ_DATA_PATH/mqft/logs/coordination_qmgr_name/loggers/logger_name.
Because running trace can affect your performance significantly and can produce a large amount of trace data, run trace with care and only when necessary. Typically, enable trace only when asked to do so by IBM® Support.
You can set further trace properties, for example trace file size and the number of trace files to keep, in the logger.properties file. These properties are described in Logger properties.
- You must run this command on the system where the logger is running.
- The traces and logging do not persist across a logger restart.
If the logger terminates and is restarted by the Process Controller process, the dynamic traces and logs are not in effect until the logger.properties file has been updated to include the required trace and log properties.
Syntax
Parameters
- -traceLogger classes=level
- Required. Level to set the logger trace and which classes to apply the trace to.
- -disableOnAnyFFDC
- Optional. If this parameter is specified, trace is disabled on the logger when it generates a First Failure Data Capture (FFDC) file.
- -disableOnFFDC ffdc_specification
- Optional. If this parameter is specified, trace is disabled on the logger when it generates a
First Failure Data Capture (FFDC) file that matches the ffdc_specification.
ffdc_specification is a comma-separated list of values. The value can be one of
the following formats:
- class_name
- The name of the class where the FFDC originated. For example,
com.ibm.wmqfte.classA. - class_name:probe_id
- The name of the class and the probe ID of the location in the class that the FFDC originated
from. For example,
com.ibm.wmqfte.classB:1.
- -jc
- Optional. Requests that the logger generates a Javacore file. The IBM service team might request that you run the command with this parameter to assist with problem diagnosis. You cannot use the -jc parameter with any other parameter.
- -p configuration_options
- Optional. This parameter determines the set of configuration options that is used to set the logger trace level. Use the name of a non-default coordination queue manager as the input for this parameter. The command then uses the set of properties files associated with this non-default coordination queue manager.
- logger_name
- Required. The name of the Managed File Transfer Logger that you want to set the trace level for.
- -? or -h
- Optional. Displays command syntax.
Example
In this example, the trace level is set toall for
all classes for LOGGER1:
fteSetLoggerTraceLevel -traceLogger com.ibm.wmqfte=all LOGGER1 In this
example, the trace level is set to all for the classes
com.ibm.wmqfte.logger.logger and com.ibm.wmqfte.cmdhandler for
LOGGER1:
fteSetLoggerTraceLevel -traceLogger com.ibm.wmqfte.logger.logger,com.ibm.wmqfte.cmdhandler=moderate
LOGGER1 fteSetLoggerTraceLevel -traceLogger com.ibm.outer=verbose LOGGER1
fteSetLoggerTraceLevel -traceLogger +com.ibm.outer.inner=off LOGGER1
Return codes
| Return code | Description |
|---|---|
| 0 | Command completed successfully |
| 1 | Command ended unsuccessfully |
