TS/MP 2.5 System Management Manual

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. In either case, the operating system responds to your command by
creating and starting the primary PATHMON process, as shown in Figure 11 (page 36).
Figure 11 Starting the PATHMON Process
Always provide a name for your PATHMON process. You use this name to identify the PATHMON
process when you communicate with the PATHMON process through PATHCOM. (If you do not
supply a name, the system gives the PATHMON process a default name, $X984. HP recommends
that you provide your own PATHMON name, which is easier to remember.)
The name you choose for the PATHMON process must start with a dollar sign ($) followed by one
to five alphanumeric characters, or if the PATHMON name is used across a network, then one to
four alphanumeric characters. The first alphanumeric character must be a letter.
CAUTION: If multiple Pathway environments are configured on a node, do not assign the name
$PM to any PATHMON process on that node. Your commands might be applied to the wrong
PATHMON environment.
$PM is the default name used when someone opens communication with PATHCOM without
specifying a PATHMON name. Suppose that your PATHMON environment runs under the
PATHMON named $PMX, but you forget to specify this name. PATHCOM attempts to direct
subsequent commands to a PATHMON process named $PM; if a PATHMON process with this
name exists, your commands are applied to the wrong PATHMON environment.
RUN Options
In addition to the PATHMON name, two other parameters, processor and NOWAIT, are generally
specified in the RUN command. These parameters are Guardian RUN options that take effect
when the PATHMON process begins execution.
The processor attribute indicates the processor in which the primary member of your PATHMON
process pair runs in a multiprocessor environment. You can select any processor for this purpose.
If you do not specify a processor, the system selects a processor at random. Using the default value
can result in an error if the PATHMON process later attempts to start the backup process in the
same processor. In Figure 11 (page 36), the primary PATHMON process runs in processor 3.
In a single-processor environment, the PATHMON process always runs as a single process in the
only processor available, whether or not you specify the processor attribute.
The NOWAIT parameter requests the TACL command interpreter to run the PATHMON process
under the NOWAIT RUN option. You specify this option so that 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 “Maintaining a PATHMON
Environment” (page 80).
36 Starting and Stopping a PATHMON Environment