Log and Trace Files
The DATABridge Client produces log files and trace files. This topic describes these files and the differences between them.
The log file contains information about errors that the client encounters and statistics that are useful in tracking performance problems. Additionally the log contains messages that are useful when reporting problems to Attachmate Technical Support (for example, versions of the various host components). When a command is executed for a data source, one or more messages appear onscreen and are written to the log file for that data source. Log files are created in the logs subdirectory of the data source's working directory. Log files are named
where db is a user configurable prefix that can be redefined in the configuration file and yyyymmdd is the date the log file was created. A time (_hhmnss) is appended to the filename if the filename is already in use. (For details about configuring the log via the filesee Exporting and Importing Configuration Files.)
If more than one log file is created for a data source on the same date, the time of day is included after the date to make the filename unique (for example, dbyyyymmdd_hhmnss.log).
Some messages are written only to the log file. These messages generally include information that may be useful when reporting problems to Attachmate Support, such as version information for the various host components.
Tracing is a powerful option that provides details on the internal processing of the DATABridge Client.
Note: Trace files are only required if you experience a problem that requires further diagnostics by Attachmate Technical Support. Do not enable tracing during routine operations as the trace files tend to be huge. You can delete these files when you no longer need them.
Trace files are named
where trace is a user configurable prefix and yyyymmdd is the date the trace file was created. The file extension is .log. If more than one trace file is created on the same date, the time is added after the date to make the filename unique. Trace files are written to the working directory for the data source.
To create a trace file, you can use the available options in the Client Console or specify the -t nnn option. The parameter nnn is a bit mask that enables various trace options. If you select a bit mask that contains 1, log messages are also written to the trace file.