FCS Trace

The server diagnostic trace tool is very helpful in debugging processes. The trace tool allows FCS trace information to be sent to a file or to standard output. When FCS trace is enabled on the MCS, both the MCS and FCS processing the request will have tracing enabled.

The ematrix.debug=true tool can also be used to enable debug.

For more information, see the "Managing Standard FCS Logs" section of the "Configuring FCS" topic.

This page discusses:

MQL Command for Tracing FCS

Tracing for FCS can be turned on (and off) using the following MQL command:

trace type fcs |filename FILENAME |;

               |on                |

               |off               |

               |text STRING       | 

filename FILENAME Clause

Specifying a file with the filename FILENAME clause turns the specified type of tracing on, and redirects the output to the specified file. There is no need to use the keyword "on". If a filename has already been specified for another type of tracing within the current session, that filename will be used, and the one specified here will be ignored, but the tracing will be enabled.

The SLF4J/logback is used to define the output log file in the appender section of the logback.xml configuration file.

If the filename specified for any tracing already exists in the directory MX_TRACE_FILE_PATH, that existing file will be copied to a backup whose name is constructed by prepending a time-specific prefix to the filename, in the form "yyyymmddhhmmss__FILENAME."

On Clause

The on modifier will turn the specified tracing on and send the trace information to stdout, unless a trace file is already in use by another type of tracing.

Off Clause

The off clause turns the specified type of tracing off. If other types of tracing have been turned on, they will stay on. Tracing that is turned on via .ini file settings can be turned off only by using the keyword all. For example:

trace type fcs off;

trace type all off;

When all types of tracing directed at the same file are turned off, the file is closed. In order to resume tracing to a file, any subsequent command must specify a filename. If it doesn't, tracing will be resumed with stdout as the destination.