Command Execution Log List Display command

You can display a record or records in the Command Execution Log file in a list format. The displayed content is output to the standard output. You can write the content to a file and output it to a printer by using the symbols for redirection (greater than, >) and pipe (vertical bar, |).

= Remarks =

The Command Execution Log files backed up by automatic or manual rotation become the target of this command as well.

Format of command

utlopllist -cl 
        [-list|-csv] [-h hostname] [-usr userID|-admusr userID] 
        [-op operation] [-prcid processingID] 
        [-from Date1 [-ftime hhmmss1]] [-to Date2 [-ttime hhmmss2]]

Explanation of the parameters

-cl

Specification of the Command Execution Log (Mandatory)

-list|-csv

Output format (Optional)

-list:: Main fields are output in fixed length format. For the fields to be output, refer to Table 5.6 Fields Displayed in Command Execution Log File.
-csv:: All fields are output in CSV format. For the format of the operation logs, refer to the following appendix:

HULFT10 for Linux/AIX Administration Manual : File format of operation logs

If omitted, the fields are rearranged so that a single main field is output per line.

-h hostname

Name of the host that started the operation whose records are to be displayed in a list format (Optional)

Specify the host name as an alphanumeric character string within 68 bytes.

When omitted, all the hosts become the targets of this command.

-usr userID

User ID (OS) on the host that started the operation whose records are to be displayed in a list format (Optional)

Specify this parameter within 561 bytes.

When omitted, all the users become the targets of this command.

You cannot specify this parameter and -admusr at the same time.

= Remarks =

The user ID of the operating system is subject to the conventions of the operating system on the starting host. For details, refer to the following:

HULFT10 for Linux/AIX Administration Manual : Outline of operation logs

-admusr userID

User ID for Management Console Security on the host that started the operation whose records are to be displayed in a list format (Optional)

Specify this parameter as an alphanumeric character string within 32 bytes.

When omitted, all the users become the targets of this command.

You cannot specify this parameter and -usr at the same time.

= Remarks =

For details on the user ID of the Management Screen Security of each host type, refer to the following:

HULFT10 for Linux/AIX Administration Manual : Outline of operation logs

-op operation

Name of the request, command, or command execution key whose records are to be displayed in a list format (Optional)

If omitted, all the requests, commands, or command execution keys become the targets of this command.

= Remarks =

For details on the names of the requests, commands, and command execution keys that you can specify, refer to the following:

HULFT10 for Linux/AIX Administration Manual : ommand execution keys and search keys

-prcid processingID

Latest identifier of the record or records to be displayed in a list format (Optional)

Specify this parameter as an alphanumeric character string in 34 bytes.

When omitted, all the latest identifiers become the targets of this command.

= Remarks =

For details on transaction identifiers, refer to the following:

HULFT10 for Linux/AIX Administration Manual : Identifier

-from Date1 [-ftime hhmmss1] -to Date2 [-ttime hhmmss2]

Start date (time) and end date (time) for the range of records to be displayed in a list format (Optional)

Specify a numeric string within 8 bytes.

The date should be specified in the date format that is specified for Date Format (datefmt) in the System Environment Settings.

It is necessary to specify the date in the range of Date1<=Date2. The specified Date1 and Date2 will also be included in the list display.

Specify the time in the format of hhmmss. If Date1 and Date2 are the same date, it is necessary to specify the time in the range of hhmmss1<=hhmmss2. The specified hhmmss1 and hhmmss2 will also be included in the list display.

When you specify time by using one or both of '-ftime' and '-ttime,' the dates '-from' and '-to' are mandatory.

When both '-from' and '-to' are omitted, all the dates become the target of this command.

When you omit "-ftime", the log records at and after 00:00 on the date you specify for "-from" become the target of this command.

When you omit "-ttime", the log records up to 23:59 on the date you specify for "-to" become the target of this command.

When '-from' is omitted, all the dates up to the date specified in '-to' become targets.

When '-to' is omitted, all the dates on and after the date that is specified in '-from' become targets.

If you specify all the parameters, HULFT targets all the data within the range of Date1 and hhmmss1 to Date2 and hhmmss2.

Table 5.6 Fields Displayed in Command Execution Log File
Field Name	Field Explanation	Display Size
Field Name	Field Explanation	When Output Format Is Omitted	When -list Is Specified
DATE	Execution date and time (in the form of YYYY/MM/DD HH:MM:SS.mmm) (*1)	23 bytes	23 bytes
PROC-ID	Latest identifier	34 bytes	34 bytes
OS-USERID	User ID (OS)	Variable	32 bytes
ADM-USERID	User ID (Management Console)	Variable	32 bytes
HOSTNAME	Name of the host that started the operation	Variable	68 bytes
OPERATION	Command execution key	Variable	36 bytes
OPERATION-DETAIL	File key information	Variable	40 bytes

The date format is determined by Date Format (DATEFMT) in the System Environment Settings.

= Remarks =

If the field string is less than the display size, the sting is displayed with left alignment.
When the size of a field to be displayed is larger than that of the display size, the part that exceeded the display size is cut off.

Note

When the code set used in the operation log files is different from the locale of the operating system on which the command is run, log records that contain double-byte codes cannot be searched properly.
When you specify -from, the system searches for log records with the time or date from the top of the Command Execution Log file, and it displays the first log record and onward, of which the execution time or the execution date corresponds to the specification of -from or after.
When you specify -to, the system searches for log records from the top of the Command Execution Log file, or from the date or time that is specified with -from, and it displays the log records up to but excluding the first one that exceeds the execution time or execution date specified by -to.
Records that may corrupt the format of the output log are skipped.

Figure 5.2 Display Range of Operation Log

Output examples

Case where the output format is omitted

DATE=2014/12/25 12:12:21.005 
PROC-ID=9999999999999999999999999999999999 
OS-USERID=USER1 
ADM-USERID=ADMUSER1 
HOSTNAME=as30 
OPERATION=SEND_REQUEST 
OPERATION-DETAIL=-f SND01 -msg0 xxx 

DATE=2014/12/26 22:15:21.748 
....

Case where -list is specified

2014/12/25 12:12:21.005 9999999999999999999999999999999999 USER1                            ADMUSER1                         as30                                                                 SEND_REQUEST                         -f SND01 -msg0 xxx 
2014/12/26 22:15:21.748 999999999999999999999999999999999A USER2                            ADMUSER2                         ux10 .... 
....

Case where -csv is specified

"2014/12/25","12:12:21.005","2014/12/25","12:12:20.086","USER1","ADMUSER1","as30","999999999999 
9999999999999999999999","9999999999999999999999999999999999","as30","","SEND_REQUEST","HULFT_CO 
MMAND","-f SND01 -msg0 xxx" 
"2014/12/26","22:15:21.748","2014/12/26","22:15:20.123","USER2","ADMUSER2","ux10","999999999999 
999999999999999999999A","999999999999999999999999999999999A","ux10","",.... 
....

= Remarks =

The date format varies depending on Date Format that is specified in the System Environment Settings.

For details, refer to the following:

HULFT10 for Linux/AIX Administration Manual : Global Settings