TS/MP System Management Manual (H06.05+, J06.03+)

Maintaining a PATHMON Environment
HP NonStop TS/MP System Management Manual—541819-007
5-24
Logging Information to a Terminal
The audit logging is done when the STATUS messages are enabled. The message
format is shown below:
ddMMMyy,mm:ss <pathmon name>: STATUS - *1166* <entity name>,
AUDIT MSG - <command name> <entity type>
<status> - USER <user id>
where:
The status messages are currently logged for successful FREEZE and THAW
commands. They will continue to appear in their current format. Additionally, the audit
logs will also be captured.
Logging Information to a Terminal
The initial log file is the OUT file for the PATHMON process. In interactive mode, this is
typically your command terminal.
When you use your command terminal for logging, you can get immediate information
from the PATHMON process. You should restrict the activity on that terminal, however,
to avoid interfering with the PATHMON messages; in fact, if you use a terminal for
logging, it is best to have that terminal dedicated to logging.
If you must use a terminal as the logging file, type “pause” at the TACL prompt to
suspend the TACL process so that logging can occur.
Logging Information to a Disk File
To select a destination other than your terminal for logging information, you can enter a
run option with the implicit RUN PATHMON command, as follows:
5> PATHMON / NAME $PMX, CPU 3, NOWAIT, OUT LOGPMON/
Alternatively, you can specify the file for logging output by using the PATHCOM
commands LOG1 and LOG2. For example, to specify $0 as the log file for errors
ddMMMyy,mm:ss
Displays date and time.
<pathmon name>
Displays the PATHMON process name that sends the message.
<entity name>
Displays the entity name.
<command name>
Displays the command, which is issued with these possible
values: ALTER, ADD, DELETE, FREEZE, STOP, THAW, START,
and ABORT.
<entity type>
Displays an entity name such as, TCP, TERM, SERVERCLASS
and so on.
<status>
Displays the status as failed or successful.
<user id>
Displays the ID of the user who issued the command.
Note. The security logging feature is supported by TS/MP 2.4 and is available only on systems
running J06.05 and later J-series RVUs and H06.16 and later H-series RVUs.