TS/MP System Management Manual (G06.24+, H06.03+)
Configuring Objects in a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
3-6
Specifying Node Independence
additional help, contact your HP representative for details about performance classes
offered and for a description of services available from service provider.
Specifying Node Independence
You can avoid hard-coding node names for many Guardian file names and other
variable names in your PATHMON environment by setting the NODEINDEPENDENT
attribute of the SET PATHWAY command to ON. When NODEINDEPENDENT is ON,
unspecified node names for processes and devices default to the node where the
PATHMON process is running after cool start.
Specifying node-independent names for processes and devices facilitates switching
your PATHMON application to another node, either in the event of failure or as part of
a planned migration (for example, in a configuration that uses Nomadic Disk
technology). When the PATHMON process is cool started on a different node, the
unspecified node names resolve to that node, thereby migrating the associated
objects.
This command establishes node independence for objects in your PATHMON
configuration, unless a node name is explicitly specified for a given object:
= SET PATHWAY NODEINDEPENDENT ON
When the NODEINDEPENDENT attribute is ON, any unspecified node names in the
Guardian file names defined for processes or devices are automatically set to \*, a
generic node name designating the node where the PATHMON process is currently
running. NonStop TS/MP and Pathway/iTS both support objects that can be
configured as node-independent—SERVER objects, for example, as well as TERM
and PROGRAM objects and TCPs. For the complete syntax and a list of object
attributes containing Guardian file names, see the SET PATHWAY Command on
page 11-12.
When to Set Node Independence
If you choose to use the NODEINDEPENDENT attribute, specify it early in your
PATHMON configuration session to ensure that it applies to other global parameters,
for example, the PATHMON dump file. Once set, the attribute applies to all
subsequent SET commands. The setting has no effect on previously specified SET
PATHWAY commands.
Node Independence and the CMDVOL Command
Setting the Pathway NODEINDEPENDENT attribute to ON overrides and disables the
node field of the CMDVOL command. See CMDVOL Command on page 10-3.
Some Names Are Always Node-Independent
Note that some object names are node-independent regardless of whether you use the
NODEINDEPENDENT attribute or not. These include the names of log files in which