FTM SWIFT trace directories

FTM SWIFT produces trace files on each system where a broker server runs. These files are stored in the following trace directories:

On each system where a broker server runs:

Main trace directory

This directory contains trace data from base, SIPN FIN, FMT FIN, and MSIF services, and from enterprise applications such as the MER Facility and RMA. Each execution group requires 20 MB for trace information in this directory each time the broker is started. To ensure that enough space is available, delete obsolete trace files from this directory. How to do this is described in Deleting trace files.
The default directory is /var/ftmswift_v300/run/trace. You can customize the name in the FTM SWIFT system configuration file dni.conf. To use different versions of dni.conf when running multiple instances in one system you configure the environment variable DNI_CONFPATH. For more information refer to Creating directory structures.

SFD initialization trace directory

The directory /tmp/dnfitrc contains trace data created during the initialization of the SWIFTNet FIN Daemon (SFD) for an LT. The name of this directory cannot be customized. The trace files in this directory have names of the form:

lt_name.dnfcfsfd.trc

For the SFD client process.

lt_name.dnfcfsfs.trc

For the SFD server process.
For each LT:
LT trace directory
This directory contains trace files written by the finite state machine (FSM) of the SWIFTNet FIN Daemon (SFD) associated with a SWIFTNet FIN LT session:

Processing trace file

This file records the processing of the SFD for a particular LT. Each processing trace file has an unlimited size, so you will need to delete older files periodically.

PDU trace files

These files record information about the protocol data units (PDUs) processed by an SFD. The size of each PDU trace file is determined by how the PDU trace is configured.

This directory has a name of the form:
```
fsm_instance_dir/lt_name/trc
```
where fsm_instance_dir represents the FSM instance directory, which is configured separately for each LT as described in Configuring a master LT.
Client trace file
This directory contains external SFD functions for the client, for example, DB2® interface, IBM® MQ interface, and base services such as Audit and Event. Each LT requires 10 MB in this directory for trace information. This directory has a name of the form:
```
dnitrace/xfsm/lt_name/cli
```
where dnitrace represents the trace directory that is specified in the FTM SWIFT system configuration file dni.conf. The default directory for dnitrace is:
```
/var/ftmswift_v300/run/trace
```
Server trace file
This directory contains external SFD functions for the server, for example, DB2 interface, IBM MQ interface, and base services such as Audit and Event. Each LT requires 10 MB in this directory for trace information. This directory has a name of the form:
```
dnitrace/xfsm/lt_name/srv
```
where dnitrace represents the trace directory that is specified in the FTM SWIFT system configuration file dni.conf. The default directory for dnitrace is:
```
/var/ftmswift_v300/run/trace
```

Make sure that you have a procedure in place to delete old trace files regularly to avoid unnecessary space consumption. For information about how to delete old trace files, see Deleting trace files. For production systems, also make sure that trace files are archived before being deleted from the runtime systems. Historic trace data can be important for problem analysis.

During normal FTM SWIFT processing, only errors are traced, so the maximum size required for trace information probably will not be reached. However, your IBM service representative might require larger traces for problem analysis, so ensure that it is possible to extend the HFS or zFS if necessary.

FTM SWIFT components that run on an application server can also produce trace files. Whether these trace files are written and their location depend on the settings that were chosen when the trace was activated on the administrative console. For more information, see Tracing enterprise applications.