Pathway/XM System Management Manual

PXMCOM Commands
Compaq NonStop™ Pathway/XM System Management Manual426761-001
11-41
LOG1 and LOG2
LOG1 and LOG2
These commands name the files that are used globally by all PATHMON processes and
TCP processes in the Pathway/XM environment for reporting errors and changes in
object status. The PATHMON processes generate messages in the specified format.
Event messages are used for reporting to an operator or application program through the
Event Management Service (EMS), a part of Distributed Systems Management (DSM).
file-name
specifies the name of a file to receive error reports and changes in status from all
PATHMON and TCP processes in the Pathway/XM environment, or the name of a
process used to collect the log messages.
If you specify a disk file, the file must exist. You must create the file, by using the
command interpreter or the FUP CREATE command, before issuing a LOG1 or
LOG2 command.
If you use FUP CREATE with no other create specifications to create a file, the file
is unstructured. The PATHMON process must determine the record length to
properly pad short records with blanks for generating 132-character length records.
Therefore, if the file is an unstructured disk file, the record length is obtained from
the SIO file control block. If a 0 is returned, the PATHMON process defaults to 132.
LogEvent does not check the file control block and always selects a 132-character
record length.
You need not specify a fully-qualified file name for a log file. If you leave the
physical node name unspecified, the log file must be on the same physical node in
which the PXMCFG process ran.
If you omit this attribute, the current log file is closed.
EVENTFORMAT
specifies that messages should be formatted as event messages. If you omit
EVENTFORMAT, text messages are generated.
STATUS
sends status change messages and error messages to the file you specify with
file-name. If the STATUS option is not specified, only error messages are
written to the log file.
LOG1 [ file-name [ , { EVENTFORMAT | STATUS } ]...
LOG2 [ file-name [ , { EVENTFORMAT | STATUS } ]...
Caution. If you turn off logging by closing a current log file, all internally queued messages are
lost.