Points to be noted on operation logs
Execution Time/Execution Date
-
If the dates that are set in the operating systems of each host are not the same, it might not be possible to display the operation logs in a list by date.
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.
-
If a user ID is not indicated by the starting point host, "N/A" is output as the user ID. Do not use "N/A" for the user ID.
Identifier
-
If an error occurs before HULFT obtain an identifier from a starting point host, the operation log is not output to the execution host.
-
There is no guarantee 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
-
If the value of a -msg parameter for utlsend, utlrecv, or the like contains a double quotation, the CSV format of the operation log may be delimited incorrectly.
Example: " cannot be used for -msg messages in utlsend.
Rotation of Operation Log files
-
When the number of backups exceeds the setting in Operation Log Generations (oplgenerationcount) due to rotation of the Operation Log files, backup files are overwritten chronologically, beginning with the oldest file. Save backups on the log server and the like at regular intervals, as necessary.
Restriction on outputting the operation log
-
If you use a version of HULFT lower than Ver.7, operation logs are not output.
Figure 2.43 Restriction on Outputting Operation Log
Errors concerning operation logs
-
Error messages are output to the syslog of the operating system when the output or rotation of the Operation Log files has failed. For details, refer to the following:
HULFT10 for Linux/AIX Error Codes and Messages :