Outline of Operation Log

Operation logs are output when a request is issued to HULFT, a command of HULFT is executed, or a system file is accessed by HULFT.

The operation logs output by the Send and Receive processes are shown below:

Figure 2.41 Operation Logs in Send and Receive Processes

1) When the Send File is issued on the Management Console or in the command line, the date of issuing the request, the User ID, the Host Name, and the like are output to the Command Execution Log of HULFT on the sending side.

2) When the Send process is executed based on the Send File and a Send Log is added, the date when the log was added, the information that identifies the added log, and the like are output to the File Access Log of HULFT on the sending side.

3) When the Receive process is executed and a Receive Log is added, the date when the log was added, the information that identifies the added log, and the like are output to the File Access Log of HULFT on the receiving side.

File Access Log and Command Execution Log

The records of file access and the records of request issuance or command execution are output to separate logs. (The File Access Log and the Command Execution Log, respectively)

You can specify the library to which the log is output as Operation Log Output Destination Library (OPLLIB) in the System Environment Settings.

Table 2.14 Variety of Operation Log
Variety of Operation Log	Output Destination	Explanation
File Access Log	<Set point of OPLLIB>/ FILELOG	The Log is output when information is added, updated, or deleted in system files, such as System Environment Settings, system management information, and various logs and the like
Command Execution Log	<Set point of OPLLIB>/ CMDLOG	The Log is output when a request is issued or a command is executed

Refer to Format and reference keys in operation logs for target system files, target types of file access, and target requests or commands of operation logs.

= Remarks =

The File Access Log is output when the contents in the system file are modified. Mere reference of the file without modification does not output the Log.
The Command Execution Log is output by the host on the side where a request or command was executed. The Observe Log as well as the File Access Log that carries the record of the addition in the Observe Log are output by the host on the side where a request was acknowledged.
Where the multiple records are deleted from system management information or logs by specifying the target range, the Command Execution Log outputs only one entry, while the File Access Log outputs one entry per deleted record.
The operation logs do not target internal behavior of the system because the log aims at keeping the record of the operation by users.

Information Output to Operation Log

Information output to the operation log is divided roughly into following categories: information on request issuance or command execution that is an origin of a series of transaction (starting point information), information on the transaction performed according to request issuance or command execution (transaction information), information specific to the File Access Log, and information specific to the Command Execution Log.

The following information is output to the operation log in CSV format:

Starting Point Information

Starting point information is the information at the time when request issuance or command execution is started. The information is notified to the connection destination, and the same information is used by all the File Access Logs and the Command Execution Logs within one transaction.

= Remarks =

The fields other than user ID in starting point information are always notified to the connection destination when the operation log output function is used.

Execution Start Time/Execution Start Date

Time and date that request issuance or command execution started

It is a date set on OS of starting host.

User ID (OS) and User ID (Management Console)

User ID of the user who performed operation

They are OS user ID of starting host, and the user ID of the Management Console that issued the request, respectively.

Their definition varies depending on the types of starting host:

Table 2.15 Difference between Definition of User ID (OS) and User ID (Management Console) by Host Types
Host Type	User ID (OS)	User ID (Management Console)
Mainframe	User ID of OS	User ID of the user who used the Management Console
UNIX/Linux	User Name of OS	Same as 'User ID (OS)' (When the Management Console Security is disabled, indicated as "")
Windows	User Name of OS	User Name registered on the Management Console Security (When the Password is disabled, indicated as "")
IBMi	User ID of OS	Same as 'User ID (OS)' (When the Management Console Security is disabled, indicated as "")
HULFT Manager	User Name of OS	User ID (Management Console) of HULFT at connection destination
HULFT-HUB Server	User Name of OS	Always indicated as " " because there is no Management Console
HULFT-HUB Manager	User Name of OS	The User Name that logged on HULFT-HUB Server

Note

For details on the conversion of character codes for the user ID (for OS) sent to the receiving-side host or to the request receiving host, refer to Points to be noted when specifying multi-byte characters in a message in Points to be Noted Regarding Message Transmission in Message Transmission.

Starting Host Name

The name of local host that performed the operation

Refer to Handling of local host name for details about the Local Host Name.

Identifier

Identifier of transaction

In each transaction, different identifier is generated. There are two types of identifier: 'Latest Identifier' and 'Starting Identifier.' Refer to Identifier for the Latest Identifier and the Starting Identifier.

Identifiers can link the record output to the operation log files with the record in the Send/Receive/Observe Logs, because they are output to the Send/Receive/Observe Logs.

Transaction Information

Transaction information is the information at the time when a file is accessed, or request issuance or command execution is processed.

Execution Time/Execution Date

Time and date when file access, or request issuance or command execution was processed

It is a time and date set on OS of execution host.

Execution Host Name

Local Host Name of the host to which file access, or request issuance or command execution was processed

Refer to Handling of local host name for details about the Local Host Name.

Operation Log User-specified Character

Character string to identify HULFT that outputs the operation log

The Operation Log User-specified Character is a character string to identify which HULFT outputs which operation logs, when the operation logs output by two or more HULFTs are accumulated.

Table 2.16 Values Set to Operation Log User-specified Character
Host Type	Values Set to Operation Log User-specified Character
Mainframe	Operation Log User-specified Character in the System Environment Settings
UNIX/Linux	HULFT Identifier in the System Environment Settings
Windows	Operation Log User-specified Character in the System Environment Settings
IBMi	HULFT Identifier in the System Environment Settings
HULFT Manager	User-specified Character in the System Environment Settings
HULFT-HUB Server	Service Name in the System Environment Settings
HULFT-HUB Manager	User-specified Character in the System Environment Settings

Specific Information to File Access Log

Specific information to the File Access Log is the information on the types and objects of file access. It is output only to the File Access Log.

Refer to Format and reference keys in operation logs for the list of the output values.

File Access Type

Types of file access

The File Access Type means varieties of operation, such as addition, modification, deletion and the like.

System File Type

The system file that is an object of file access

It is an identifier that indicates the object system file of file access.

File Key Information

Fields in the file that are objects of file access

The File Key Information is an additional information to identify the record that was accessed, when two or more records are stored in one file, such as system management information, or Send/Receive/Observe Logs and the like.

Specific Information to Command Execution Log

Specific information to the Command Execution Log is the information on the processed requests or commands. The Information is output only to the Command Execution Log.

Refer to Format and reference keys in operation logs for the list of the output values.

Command Execution Key

Varieties of requests or commands

It is an identifier that indicates the processed requests or commands.

Command Issued by

Issuer of requests or commands

It is an identifier that indicates the source of requests or commands, such as whether the command was executed in the command line, and whether the request was issued on HULFT Management Console.

Command Parameter

Parameter of the command

The Command Parameter is a parameter specified when the parameter command is executed.