TS/MP 2.5 System Management Manual

specifies that messages must be formatted as event messages. If you omit EVENTFORMAT, text
messages are generated.
Considerations
• The OUT file initially specified with the PATHMON RUN command becomes the initial LOG1
file until you specify otherwise by issuing a logging command. The file is opened when you
specify the STATUS attribute
• As a best practice, specify a disk file for logging than a terminal because log messages are
lost after they scroll off the terminal screen. Also, performance is generally better to a disk file
than to a terminal.
If the logging file is a terminal, as a best practice, use that terminal only for logging. If that is
not possible, restrict the activity on that terminal to avoid interfering with messages from the
PATHMON process. In either case, type “pause” at the TACL prompt to suspend the TACL
process so that logging can occur.
NOTE: If a logging terminal is unavailable, the PATHMON environment might slow down
and be unable to support transaction processing.
• EDIT files are not acceptable log files to the PATHMON process. If you attempt to use an EDIT
file for a log, the PATHMON process returns an error and fails to open the log.
• If a logging command is used with no attributes, the corresponding log file is closed.
• Logging of status messages is automatically disabled during execution of the SHUTDOWN2
command.
Examples
This command sends error information to a terminal:
LOG1 $TERM1
This command logs errors and status change messages in a file named COMPLOG:
LOG2 COMPLOG,STATUS
This command logs errors and status change messages to $0, and formats the messages as event
messages:
LOG1 $0, EVENTFORMAT, STATUS
This command closes the LOG2 file:
LOG2
PRIMARY PATHMON Command
Use the PRIMARY PATHMON command to resume operation of the PATHMON primary process
in the processor defined for this process in the PATHMON configuration file. Use this command
after an individual process or processor failure, or after a SWITCH command has moved the
PATHMON primary process from one processor to another.
PRIMARY PATHMON [ , IFPRICPU number ]
IFPRICPU number
specifies the processor in which the PATHMON primary process is to run. If this processor is defined
for the PATHMON process in the PATHMON configuration file at the time that you enter this
command, the PATHMON process resumes the operation of its primary process in this processor.
If the PATHMON primary process is already running in this processor, or if this is not the processor
configured for the PATHMON primary process, the PATHMON process ignores the command.
PRIMARY PATHMON Command 157