Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ acmslog(1) — ACMSxp 3.2A

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

acms(1)

acmsadmin(1)

acmsdbx(1)

stdl(1)

acms_create_tpsystem(1)

acms_delete_tpsystem(1)

acms_set_version(1)

acms_start_tpsystem(1)

acmsxp_introduction(1)

acmslog(1)  —  Commands

Digital

NAME

 
acmslog − Displays an ACMSxp event log

SYNOPSIS

 
 acmslog [-b [dd-mmm-yyyy[-hh:mm[:ss]]]]
         [-d device_id... ]
         [-f { stdl | system } ]
         [-i interface_id...]
         [-l [ log_file_name ] ]
         [-o file_name ]
         [-p procedure_id... ]
         [-P principal_id... ]
         [-r request_id... ]
         [-s [dd-mmm-yyyy[-hh:mm[:ss]]]]
         [-S server_name ]
         [-T [all | { audit |
                      fault |
                      security |
                      status |
                      trace } [ ... ] ] ]
 

FLAGS

       •-b[dd-mmm-yyyy[-hh:mm[:ss]]]
 
Limits report to events occurring before the indicated date and time.
 
If flag is omitted, default is before the current date and time.
 
If -b is provided but date and time are omitted, default to the current date and time of 00:00:00.
 
If -b and date are specified, but time is omitted, default the time to 00:00:00.
 

       •-d device_id[...]
 
Limits the report to records of events logged by requests originated from the specified devices. Multiple device_ids are separated by spaces.
 

       •-f { system | stdl }
 
Specifies format of the listing.

osystem
 
Generate listing in default system format. Any of the event types can be specified with this format. For audit events, only the header part of the event is displayed.

ostdl
 
Converts the audit event records in the STDL-compliant format. Only the audit type can be specified with this format. Generates an error if other than audit event types are specified with this format, or if an output file is not specified with the -o option flag. 

 

       •-i interface_id[...]
 
Limits the report to events generated by procedures in the specified interface. Multiple interface_ids are separated by spaces.
 

       •-l [log_file_name]
 
Specifies a log file from which the event records are read. Supply a full path, a relative path, or a file name.
 
If log_file_name is not specified and the ACMS_LOG_FILE environment variable is not defined, ACMSxp prompts for a file name. For example:
 

Enter the log file name :

 
If -l is omitted, the event records are read from the file indicated by the ACMS_LOG_FILE environment variable. 
 

       •-o file_name
 
Specifies the output file to which the report is written. Note that the redirect (>) capability can be used to perform the action. If omitted, the report goes to the standard output. The value for file_name can be a full path specification, otherwise the file is created in the current directory. 
 
The -o flag is required when -f stdl is specified. 
 

       •-p procedure_id [...]
 
Limits the report to events associated with the specified procedure. Multiple procedure_ids are separated by spaces.
 

       •-P principal[...]
 
Limits the report to events associated with one or more specified principals. Multiple principals are separated by spaces.
 

       •-r request_id[...]
 
Limits the output to events associated with the specified requests. Multiple request_ids are separated by spaces.
 

       •-s [dd-mmm-yyyy[-hh:mm[:ss]]]
 
Specifies a date and time since which events are reported. Only events after the specified day and time are eligible.
 
If the flag is omitted, default to the earliest date and time in the log file.
 
If -s is provided but date and time are omitted, default to the current date and time of 00:00:00.
 
If -s and date are specified, but time is omitted, then default the time to 00:00:00.
 

       •-S server_name[...]
 
Limits the report to events associated with the specified servers. Multiple server names are separated by spaces.
 

       •-t tpsystem_name
 
Limits the report to events generated by processes in the specified TPsystem.
 

       •-T [all | { audit | fault | security | status | trace } [ ... ] ]
 
Limits the report to records of one or more of the event types specified. Multiple event types are separated by spaces. The event types are:

oall
 
All event types meeting the selection criteria. This is the default if you omit -f and -T. 

oaudit
 
Has two format types:

-system
 
Execution context information and application program interface

-stdl
 
Audit event record including application-supplied variable-length data. This is the default if -f stdl is specified and -T is omitted. 

 

ofault
 
Gives execution context information, severity of the fault, and text from the message catalog.

osecurity
 
Gives both information on access denials and text from a message catalog.

ostatus
 
Gives state transition, entity specification, and text from a message catalog.

otrace
 
Gives execution context information (for server), and the function entered, returned, exited, or completed.

 

DESCRIPTION

 
The acmslog utility displays the contents of the event log file to which the ACMS_LOG_FILE environment variable points.  If the ACMS_LOG_FILE environment variable is not set, the user is prompted for a file name.  The default display is standard output. 
 
If no flags are defined, all default options are applied and the log file name is:

oIf the ACMS_LOG_FILE environment variable is defined, its definition is used. 

oOtherwise the user is prompted for a log file name (exit if no response). 
 

EXAMPLES

acmslog -f stdl -o mylog_file.log

acmslog -T status fault -l mylog.log

acmslog -s 11-aug-1997-09:00 -b 11-aug-1997-10:00

acmslog -S inventory -o event_rpt.lis

acmslog -l tpsys1_audit.log

acmslog -l tpsys1_audit.log -P james
 

RELATED INFORMATION

Commands: acms(1), acmsadmin(1), acmsdbx(1), stdl(1)

Scripts: acms_create_tpsystem(1), acms_delete_tpsystem(1), acms_set_version(1), acms_start_tpsystem(1)

acmsxp_introduction(1)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026