FT logging

The following 3 commands are available for the FT logging function:

FTDELLOG	Deleting log records Deleting offline log files
FTMODOPT	Switching on/off the logging function and define the scope of logging Changing the log file Define whether log entries are to be regularly deleted and, if necessary, specify the deletion interval.
FTSHWLOG	View information on log entries Listing log file names

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 an FT logging record. The file consisting of these logging records thus represents a complete, uninterrupted documentary record of FT operation over a prolonged period of time.
openFT writes the logging records into the log file
<inst>.SYSLOGSYSLOG.Lyymmdd.Lhhmmss under the OPENFT QUALIFIER of the openFT instance.

yy = year, 2-digit.
mm = month, 2-digit.
dd = day, 2-digit.
hh = hour, 2-digit.
mm = minute, 2-digit.
ss = second, 2-digit.

The date and time designate the time (GMT) at which the log file was created. This suffix makes it possible to distinguish between the current and offline log files.

If the openFT qualifier (OPENFT QUALIFIER in FJGEN) is more than 11 characters in length then the suffix is truncated. If a "Second Level Qualifier" is defined for logging in the z/OS parameter library (LOGFILE_2ND_Q, see "ftzos_inst_en") then the suffix is truncated if, together, the openFT Qualifier and this Second Level Qualifier are longer than 23 characters. If the sum of these lengths is greater than 31 characters then the entire suffix is omitted. In this case, it is no longer possible to change the log file.

Changing the log file and administering offline log files

You can change the log file using the command FTMODOPT
LOGGING=*CHANGE-FILES. 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. You can change the log file several times and therefore manage multiple offline log files.

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

As one of your duties as FT administrator, you should regularly create backups of the log records from the current log file or from the offline log file(s) as a file in CSV format or on tape, for example and then delete the log records or offline log file(s) with the FTDELLOG command.

In this way you have a complete, uninterrupted log at your disposal for documentation purposes, while at the same time no storage capacity is wasted. Bear in mind the assigned file size of the current log file does not change when you delete log records, but the space formerly occupied by the records you delete is released within the file.

Viewing the contents of a log record

The information content of the FT logging records includes:

• date and time of request processing,

• an acknowledgment indicating correct completion of a request, or the reason for request rejection or abort,

• the direction of file transfer,

• the name of the partner system involved in file transfer,

• TSN and user ID of the request initiator for requests submitted in the local system; only *REMOTE is entered for remote request initiators,

• the user ID under which the request was handled or should have been handled,

• the name of the file,

• the global request ID for inbound requests,

• if an abort occurs, additional information on the cause.

The FT administrator can use the FTSHWLOG command to output all FT logging records of his/her system. Two formats are available for the output: a format that is suitable for listings, and a CSV format that is optimized for further processing. He/she can also choose between a brief overview or a long detailed output and use NUMBER=*POLLING(..) to repeat the output of the new log records at regular intervals.

If the FTAC functionality is being used, the logging records relevant for FTAC are saved in the same file.

Modifying logging settings

You can set the scope of the logging functions and define the times and intervals for the automatic deletion of log records.

Setting the scope of logging

You set the scope of logging with the LOGGING=SELECT(...) operand in the FTMODOPT command.

You can set the scope of FT, FTAC and administration function logging differently. Following installation, full logging is set.

Setting the automatic deletion of log records

You can set the intervals for the automatic deletion of log records in the FTMODOPT command by setting the operand DELETE-LOGGING=*PAR(..). 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. You should only enable this function if you do not require the uninterrupted recording of log records.