NET/MASTER Management Services (MS) Operator's Guide

Displaying Information About Activity Log Files
Examining the Activity Log
6–20 106379 Tandem Computers Incorporated
the first log on the log file list again (if SYSPARMS LOGWRAP=YES). Previously
logged messages are purged from the log that is being reused.
Note The PARAM and SYSPARMS commands for configuring the physical activity log files and controlling the
wrapping of logs are discussed in the NonStop NET/MASTER MS System Management Guide.
In the event that SYSPARMS LOGWRAP=NO, and there are no available log files, a
warning message informs all monitor-class operators that logging has ceased and the
system is continuing without logging.
Output from the NonStop NET/MASTER MS STATUS command also includes a
warning message if logging has been halted. All log messages continue to be passed
to the LOGPROC procedure for analysis even if no log output is possible.
You can explicitly stop logging to the current activity log file and open another
available log file with the NonStop NET/MASTER MS LOGSWAP command. This
releases the current log file if you want to make it available for printing, for example.
The syntax for the LOGSWAP command is as follows:
LOGSWAP [ n ]
where n is the number of the log file to open as the next current activity log file.
For example, to stop logging to the current activity log and open log file number 5,
enter:
LOGSWAP 5
If you are a monitor-class operator, you are advised when a swap takes place.
Note Log files should be carefully monitored to ensure that historical data is not overwritten before the file has
been archived. The log files may be required at a later stage for audit or other control purposes.
Displaying Information
About Activity Log
Files
The NonStop NET/MASTER MS SHOW LOGS command displays the start and stop
time for each defined log file, the status of each log file, and either:
The reason for swapping, if a log file has been swapped automatically, or
The user ID of the operator entering the LOGSWAP command, if a log file has
been swapped explicitly.
For example, the following SHOW LOGS output indicates that LOG1 was swapped by
SYSMAN, and events are currently being logged to LOG2:
SHOW LOGS
NNM1505 NAME STATUS START DATE TIME STOP DATE TIME SWPD BY
NNM1506 LOG1 SWAPPED 1994/11/04 15:56:39.386 1994/11/05 09:33:06.411 SYSMAN
NNM1506 LOG2 IN USE 1994/11/05 09:35:09.574
NNM1506 LOG3 AVAIL