openFT can record the results of all file transfer requests, irrespective of whether the initiative is in the local or the remote system (outbound and inbound requests, respectively). The information on each successfully completed or aborted request is recorded in a so called "FT logging record". This represents a complete, uninterrupted documentary record of FT operation over a prolonged period of time.
If FTAC is used then FTAC logging is always also performed. The FTAC functionality is always installed and activated on Unix and Windows systems. FTAC is optional on mainframe systems.
If central administration is used, ADM logging for central administration is also available.
The FT administrator has the following tasks
Setting the extent of logging via the operating parameters
For example, logging can be restricted to only those requests for which an error has occurred. FT logging can be completely disabled. However, this is not recommended if uninterrupted logging is desired.
Switching the logging file (offline logging)
Backing up and, if necessary, deleting the log records
Using the log records for diagnostic purposes, see section “Diagnostics and error correction”.
Changing the log file and administering offline log files
The FT administrator can change the log file via setting operating parameters. This closes the current log file which is nevertheless retained as an offline log file. For the following log records, a new log file is created with the current date in the suffix. The log file can be changed several times and therefore multiple offline log files can be managed.
This change-over has the following benefits:
Faster access to logging information due to smaller log files.
Improved administration of log records through regular change-overs and back-ups of the offline log files.
Possibility of performing extensive searches in the offline logging information without affecting ongoing openFT operation.
Saving and deleting log records
Depending on the volume of requests, the FT administrator should back up the log records from the current log file or from the offline log file(s) at regular intervals, for example as a file in CSV format, and then delete these log records or offline log file(s). In this way, the log records remain available to provide uninterrupted documentation over an extended period, while simultaneously ensuring that storage space is not taken up unnecessarily.
On BS2000 and z/OS systems, it should be noted that deleting log records does not reduce the assigned file size of the current log file but simply that space in the file that is no longer required is freed up.
Automatic deletion of log records
The FT administrator can set the intervals for the automatic deletion of log records. This setting deletes log records as of a defined minimum age at regular intervals and at a specified time.
This automatic delete function is only active if openFT is started. If openFT is not started at a scheduled delete time then the delete operation is not performed on the next start-up.
Following installation, the automatic deletion of log records is disabled. The FT administrator should only enable this function if the uninterrupted recording of log records is not required.