TS/MP System Management Manual (G06.24+, H06.03+)

Starting and Stopping a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
2-5
Starting and Using PATHCOM
the PATHMON process runs as a background process. TACL regains control of the
terminal as soon as the PATHMON process is created.
In addition to the processor and NOWAIT parameters, you can specify a log file in
which your PATHMON records errors and changes in object status, as shown in this
example:
5> PATHMON / NAME $PMX, CPU 3, NOWAIT, OUT LOGPMON/
For more information about logging status and error information, see Section 5,
Maintaining a PATHMON Environment.
If you do not specify these RUN options, the operating system assigns default values
for them. For instance, the operating system assigns your terminal as the default log
file device.
For more information about these and other RUN options, see the TACL Reference
Manual .
Starting and Using PATHCOM
After a PATHMON process has been started, you can start a PATHCOM process to
communicate with the PATHMON process by issuing an implicit RUN command to
TACL.
For example, this command starts a PATHCOM process that communicates with the
PATHMON process named $PMX:
> PATHCOM $PMX
You can communicate with a remote PATHMON process if, for example, you need to
configure a PATHMON environment on a remote system. If you want to communicate
with a PATHMON process on another node, be sure to use a fully qualified PATHMON
process name in your command, for example:
> PATHCOM \NYC.$PM16
You can enter this command from your terminal, as shown in the example.
Alternatively, you can create a command file that contains this command (as well as
others) and then request execution of the commands in that file. these examples show
the interactive use of PATHCOM.
The operating system responds to your command by creating your PATHCOM process
and establishing communication with the PATHMON process, as shown in Figure 2-3: