TS/MP 2.5 System Management Manual

ERROR *1017* PATHCTL FILE (file-error-num)
The PATHMON process saves the configuration values you specify in memory, as shown in Figure 10
(page 35). At startup, these values are written to the PATHMON configuration file. (For more
information, see “Configuring the PATHMON Process” (page 41).)
Figure 10 Configuring the PATHMON Process
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.
Assign a process name and start the PATHMON process that controls your PATHMON
environment.
2. Start PATHCOM.
Start a PATHCOM process that communicates with the PATHMON process. From this point
on, all your interactions with the PATHMON environment take place through PATHCOM.
3. Configure the PATHMON environment.
Use SET PATHWAY commands to specify global parameters and limits for the overall
configuration.
Use SET PATHMON commands to specify a backup processor and request error dumping.
One of your options is to configure all processes and devices in the Pathway environment as
node-independent, making it easier to move your database to a new system. Node names
for node-independent process and device names default to the node where the PATHMON
process is currently running.
4. Start the Pathway environment.
Once these four steps are completed, you can use PATHCOM to configure the SERVER objects
controlled by the PATHMON process. Object configuration is described in “Configuring Objects
in a PATHMON Environment” (page 51). For instructions on configuring TCPs and TERM and
PROGRAM objects, see the Pathway/iTS System Management Manual.
NOTE: For starting the PATHMON environment in TS/MP 2.5, PDMCOM or PATHCOM can be
used. However, it is recommended to use PDMCOM (instead of PATHCOM) because it can
communicate with multiple PATHMONs simultaneously. For more information on PDMCOM, see
the TS/MP 2.5 Release Supplement.
Starting the PATHMON Process
To start a new PATHMON process, name the PATHMON process in an implicit RUN command to
TACL. For example, this command starts a PATHMON process named $PMX and specifies that
the process will run on processor 3:
> PATHMON /NAME $PMX, CPU 3, NOWAIT/
Starting a PATHMON Environment 35