TS/MP 2.5 System Management Manual

is the maximum number of Subsystem Programmatic Interface (SPI) processes that can run
simultaneously within the Pathway environment. SPI is part of the HP Distributed Systems Management
(DSM) facility. For more information on the SPI interface, see the NonStop TS/MP and Pathway
Management Programming Commands Manual.
number must be a value from 1 through 100. (Until a Pathway environment is started, only one SPI
process or PATHCOM process at a time can open communication with the PATHMON process.)
The default value is 1. For other limits, see “Configuration Limits and Defaults” (page 318).
MAXTELLQUEUE number
This attribute is specific to the Pathway/iTS product. A complete description of this attribute is given
in the Pathway/iTS System Management Manual.
If your environment does not support Pathway/iTS, HP recommends that you specify 0 for the value.
The default value is 4.
MAXTELLS number
This attribute is specific to the Pathway/iTS product. A complete description of this attribute is given
in the Pathway/iTS System Management Manual.
If your environment does not support Pathway/iTS, HP recommends that you specify 0 for the value.
The default value is 32.
MAXTMFRESTARTS number
This attribute is specific to the Pathway/iTS product. A complete description of this attribute is given
in the Pathway/iTS System Management Manual.
If your environment does not support Pathway/iTS, HP recommends that you specify 0 for the value.
The default value is 5.
NODEINDEPENDENT [ON | OFF]
designates whether unspecified node names in Guardian file names resolve to the node name \*,
a generic name that designates whatever node the PATHMON process is running on after cool start.
The default value is OFF.
ON
specifies \* as the default node name when the node name is left unspecified in Guardian file names
defined during the current PATHCOM session and all subsequent PATHCOM sessions.
Guardian file names with unspecified node names are stored in the PATHMON configuration file
using \* as the node name.
OFF
s Guardian file names with unspecified node names to resolve to the node name specified by the
CMDVOL command, or, if the CMDVOL is omitted, to the node of the user who started PATHCOM.
For more details on the CMDVOL command, see “PATHCOM Operation Commands” (page 137).
You can explicitly designate node-independence for any PATHMON-controlled object by specifying
\* for the node name when you define the object. However, setting NODEINDEPENDENT to ON
and then leaving out the node name when you configure an object is a simpler and more
comprehensive way to accomplish node independence.
PATHCOM checks the NODEINDEPENDENT attribute when it opens the PATHMON process. If you
want to take full advantage of the node-independence feature, set NODEINDEPENDENT to ON
early in your PATHMON configuration session. When set, the attribute applies to all subsequent
SET commands. The setting has no effect on previously specified SET commands.
Following are the file names that can be qualified by a node name when configuring a PATHMON
environment. These names are designated as nodeindependent when the NODEINDEPENDENT
attribute is set to ON.
Associated File NameObject
DUMP FILE file-namePATHMON process
OWNER owner-idPathway object
162 PATHMON Environment Control Commands