Points to be noted on operation logs

Execution Time and Date

• Displaying the records of operation logs in a list by specifying date may not work correctly if the date set on the operating system of each host is not the same.

User ID

• Executing a command does not output anything in the field of the user ID (Management Console).

• Failure to obtain a user ID outputs 'FAILED' as the user ID. Do not use the term 'FAILED' for the user ID.

• When the starting host does not notify the execution host of the user ID, 'N/A' is output as the user ID. Do not use 'N/A' for the user ID.

Identifier

• If an error occurs before the Identifier is obtained from the starting host, the execution host does not output the operation log.

• It is not guaranteed that HULFT will not generate the same Identifier in the future. The same Identifier might be generated for a different transaction depending on the circumstances.

Output Strings

• When you specify a character string in a parameter such as a message parameter of the Send File program (XRSNDGO) or the Send Request program (XRRCVREQ), using a double quotation (") prevents the operation logs from handling the string correctly as CSV.

Operation Log Switch

• Backups of the operation logs are generation files. When backup files strain disk space or when the number of backups exceeds the generation setting, backup files may be overwritten. Save the backups on a server or another computer used for operation log management at regular intervals, if necessary.

Restriction on Outputting Operation Logs

• When the version of the starting host or the executing host is lower than HULFT Ver.7, the operation logs are not output.

  

  Figure 2.41 Restriction on Outputting Operation Logs