2.14 NAME

112

SysDbgFile

An alphanumeric string which specifies where the debugging information is recorded. This argument can be used in two ways:

If the character "." (a dot) is specified, FSE processes will write their debugging data in corresponding files with file names of the form <ProgramName>_<ProcessID>.log. Each generated log file will correspond to a single running FSE process;

If string other than "." is specified, it will be considered as a file name for single FSE debug file, where all running FSE processes will write their debugging information into.

In both cases the log file(s) will be put in the directory /var/opt/fse/log/debug (on Linux systems) or %InstallPath%\var\log\debug\ (on Windows sys- tems).

This argument can only be used in combination with the SysDbgLevel ar- gument. If it is not used, each FSE process writes the debugging data to its corresponding standard output stream (stdout).

SysDbgFlags

A string composed of one or more (different) uppercase letters from the set {"I", "N", "C", "T", "E", "V"}. This argument specifies in detail which events in the running FSE processes are logged and defines the form of the debug output in an FSE debug file. The letters have the following meaning:

I .......... Function in & out. Specify that entries and exits from func- tions should be logged. This choice results in large amounts of debug- ging information.

N .......... No–header form. Specify that no FSE debug file header is printed.

C .......... Compact–header form. Specify that a compact FSE debug file header instead of the full one is printed.

T .......... Exception throw. Specify that all events that cause an excep- tion throw should be logged.

E .......... Error occurrence. Specify that major errors which occur in the FSE processes should be logged. Note that such errors are nor- mally only logged in the FSE error log file.

HP StorageWorks File System Extender Software CLI reference