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

Starting and Stopping a PATHMON Environment

NonStop TS/MP System Management Manual—541819-001

2-8

Starting and Using PATHCOM

that you want PATHCOM to read. A command file can be an IN file or an Command

file: the only difference lies in how you execute the file.

IN Command

You specify the IN command when you start PATHCOM. For example, this command

starts PATHCOM and directs PATHCOM to read commands from a file named

PWCMD and list them on the device $S.#LP:

11> PATHCOM /IN PWCMD, OUT $S.#LP, CPU 1, NOWAIT/ $PMX

When PATHCOM runs, it reads the commands and executes them in sequence.

When it encounters an end of file or an EXIT command, PATHCOM terminates.

OBEY Command

You specify the OBEY command from within PATHCOM. For example, this command

directs PATHCOM to read commands from a command file named PWCMD:

8> PATHCOM $PMX

$X364: PATHCOM - T8344D42 - (30JUL96)

= OBEY PWCMD

TACL Routines

The TACL INLINE facility enables you to incorporate PATHCOM commands into a

TACL routine to manage your PATHMON environment. This example shows a few

lines from a TACL routine that starts server objects in the PATHMON configuration file:

pathcom/inline,cpu 1,pri 190 / %1% == assume local pmon

+ errors 999

[#loop |do|

#set count [#compute [count] + 1 ]

+ start server srvr-S[count]

|until| [count] >= 50

]

For more information about TACL and using TACL routines, see the

TACL Reference

Manual

and the

TACL Programming Guide

Using DEFINEs

You can use DEFINEs to specify names for the files that PATHCOM uses directly as

command files. For example:

12> ADD DEFINE =CMD-FILE, CLASS MAP, FILE $DATA.PW.CONFIG

13> ADD DEFINE =OUT-FILE, CLASS SPOOL,LOC $S, REPORT “CONFIG”

14> PATHCOM/IN =CMD-FILE, OUT =OUT-FILE/ $PMX