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

Starting and Stopping a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
2-2
Starting a PATHMON Environment
system, the PATHMON process uses the information stored in this file to create its
operating environment.
Assigning the PATHMON Configuration File
The PATHMON configuration file is always automatically created on the node where
the PATHMON process is running. Also, unless you specify otherwise, the PATHMON
process operates as if the PATHMON configuration file is located in its default volume
and subvolume, under the name PATHCTL.
You can, however, assign unique names to the PATHCTL file by using the ASSIGN
command prior to starting the PATHMON process. For example, this ASSIGN
command, entered at the TACL prompt, specifies a configuration file named PMCNTL
on subvolume B of volume $A:
38> ASSIGN PATHCTL, $A.B.PMCNTL
Multiple configuration files with the same name−PATHCTL, for example−can exist on
the same NonStop system; however, only one file with a given name can exist on a
given volume and subvolume. If you plan to start more than one PATHMON process
from a given subvolume, you must assign a unique name to each configuration file;
otherwise, a PATHMON process may attempt to use the wrong configuration file,
resulting in this error:
ERROR *1017* PATHCTL FILE (file-error-num)
The PATHMON process saves the configuration values you specify in memory, as
shown in Figure 2-1. At startup, these values are written to the PATHMON
configuration file. (For more information, see Configuring the PATHMON Process on
page 2-11.)
Starting a PATHMON Environment
Starting a PATHMON environment consists of these steps, which are summarized in
this list and explained in detail throughout this section:
1. Start the PATHMON process.
Figure 2-1. Configuring the PATHMON Process
PATHCOM PATHMON
$PMX
Backup CPU 1
.
.
.
= SET PATHMON BACKUPCPU 1
VST010.vsd