TS/MP 2.5 System Management Manual

2 Starting and Stopping a PATHMON Environment
Steps to Starting and Configuring a PATHMON Environment
This section describes how to start, restart, and shut down a PATHMON environment. Before you
actually start a PATHMON environment, you start the PATHMON process. Multiple PATHMON
environments can run on a given node; however, each PATHMON environment includes only one
PATHMON process. The PATHMON process enforces the limits you set for the environment and
monitors the operation of all objects (for example, SERVER objects) under its control. Note that
although this section gives an overview of the steps involved in setting limits for the environment,
for complete instructions on configuring your PATHMON environment, see “Configuring Objects
in a PATHMON Environment” (page 51).
After you start the PATHMON process, you start PATHCOM, the interactive interface that allows
you to communicate with the PATHMON process. Now you are ready to enter the commands that
define the limits for your PATHMON environment. At system startup, the PATHMON process uses
these limits to create the PATHMON configuration file.
NOTE: The PATHMON environment includes the PATHMON process and the objects it controls:
SERVER objects and-if your environment includes Pathway/iTS-TCPs, TERM objects, and, PROGRAM
objects.
How the PATHMON Process Builds the Configuration File
The PATHMON configuration file, whose default name is PATHCTL, stores configuration information
about your Pathway environment. Configuration information is all the data about environment limits
and object attributes that is stored as a result of the SET, ADD, ALTER, DELETE, CMDCWD, CMDVOL,
or CONTROL commands.
When you start a new system, the PATHMON process creates the PATHCTL file using the limits
that you specify in the SET PATHWAY commands prior to startup. The PATHMON process reserves
enough disk space to store configuration definitions for all objects. For example, if you specify a
maximum of five server classes, the PATHMON process builds the configuration file with space
for five server class configurations.
When you define and add objects to your PATHMON environment, the PATHMON process fills
in the appropriate areas in the PATHMON configuration file with the object definitions. During
system operation, the PATHMON process updates the configuration file as object definitions are
added, altered, or deleted. Whenever you cool start a system, the PATHMON process uses the
information stored in this file to create the 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 the 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 might
attempt to use the wrong configuration file, resulting in this error:
34 Starting and Stopping a PATHMON Environment