Description of short output of FTSHWLOG

Short output form of FT logging records (example)

FTSHWLOG NUMBER=2

  TYP LOGG-ID    TIME       RC      PARTNER    INITIATOR INIT USER-ADM FILENAME

  2017-04-22
  T         5333 14:18:24 2169 <G133H301 FT2V292          FT2V292    TEST2

  T         5284 14:08:12 0000 >G133H301 FT2V292          FT2V292    TEST1

Short output format for ADM log records (examples)

ADM log for a remote administration request that has been issued locally:

FTSHWLOG NUMBER=1

  TYP LOGG-ID TIME      RC      PARTNER    INITIATOR INIT USER-ADM FILENAME
  2017-04-03

  A       3555 17:15:11 0000 <ftadm:/* FTV520           FTV520

ADM log record on the administered openFT instance:

FTSHWLOG NUMBER=1

  TYP LOGG-ID TIME      RC      PARTNER    INITIATOR INIT USER-ADM FILENAME

  2017-04-03

  A       9006 11:32:51 0000 >ftadm:/* *REMOTE          ftadmin

Explanation

Not all values are displayed for all log record types and request types. The table below also describes values that can occur only in ADM log records.

Name	Explanation
TYP (column 1)	Specifies if it is an FT or FTAC or ADM or FTP log record. T indicates the FT logging record, C indicates the FTAC logging record, A indicates the ADM logging record.
TYP (columns 2-3)	Definition of FT function:
	' ' V A D C M R CD MD DD L	(blank) transfer file transfer file and delete send file (only inbound possible) read file attributes delete file create file modify file attributes read directory create director modify directory delete directory login (inbound FTP access)
LOGG-ID	Number of the log record (up to twelve digits)
TIME	Time when the logging record was written
RC	Reason Code. Indicates if a request was successfully executed, or if not, why it was rejected or terminated. If an FT request is rejected for “FTAC reasons” (e.g. 0014), the exact reason behind the termination can be found in the FTAC logging record of the system that rejected the request.Further information on the reason code can be obtained using the FTHELP xxxx command.
PARTNER	Provides information about the partner system. The output in the case of named partners consists of the symbolic name, and in the case of dynamic partners of the address (up to 8 characters; if the address is longer, the last character is an'*'). The partner system is prefixed by an identifier from which you can determine the request direction.
	>	The request direction is to the partner system. This direction is specified for a send request, i.e. the data is transferred to the partner request to view remote file attributes request to view remote directories
	<	The request direction is to the local system. This direction is specified for a receive request, i.e.the data is transferred to the local system request to modify remote file attributes request to delete remote files
INITIATOR	Initiator (user ID) in the case of requests issued locally issued; if initiative is from remote system: *REMOTE
INIT	TSN from which the request came. If the INITIATOR was *REMOTE, the field is empty.The field is always empty in z/OS and is only output for reasons of compatibility.
USER-ADM	User ID in the local system used by the requests
FILENAME	Filename resp. preprocessing or postprocessing in local system. If the file is a library element, the output will be of the format <libraryname>/<type>/<elementname>[(<version>)]. In the case of ADM logging records, this field is empty. For security reasons, only the first 32 characters (or 42 characters in the case of FTEXECSV preprocessing operations) of a preprocessing or postprocessing command are taken over into the logging record. By arranging the call parameters accordingly or by inserting spaces, you can influence the command parameters that are not to appear in the logging record. FTEXECSV is the reaction to an ftexec command issued in a remote Windows or Unix system.