- File System Interface (FSI) Trace Option

This option is used to trace the File System Interface, which is used for Indexed File Types, and Sequential Files. These include PROISAM, CISAM, and the Sequential File types SEQ and BIN. (Note that SQL File Types are excluded.)

The FSI trace pre-dates the General Trace code, and sometimes the General Trace TRACEFILE option can be useful. However, the FSI trace is sometimes needed to see the internal file system specific error codes, as these get mapped by the FSI layer to generic codes by the time they get passed back to the TRACEFILE layer.

The FSI trace options are specified in the same place as the General Trace Settings.

There are several options:

FSITRACE = <options>

Where <options> are one or more of the comma separated keywords:

Option	Description
ERROR	Reports FSI error messages.
DEBUG	Reports FSI debug trace information.
ALLOC	Reports FSI Memory Allocation and Deallocation details
NETWORK	Reports remote FSI Network (Socket) send/receive debug trace information.
INFO	Analyses file type memory requirements, which can help identify any potential memory savings. It can also be used to inspect the effects of Memory File Optimisation. Click here for more information.

The FSI trace is output to the fsitraceXXXX.log. On Windows, the file is created in C:\windows\system32. On a Unix system, the file is output to the current working directory. If this file already exists, it is appended to.

The FSI trace is large (about 4 lines per operation, which includes bootstrap file read, write and delete calls).

Comment on this topic

Topic ID: 750020