Pathway/iTS System Management Manual (G06.24+)

Configuring Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
2-5
Specifying Node Independence
choose your parameters very carefully. Once you start your PATHMON environment,
you cannot alter these limits without shutting it down for complete reconfiguration.
It is recommended that you always allow some space for growth. For example, if you
are not certain whether you might need an extra TCP, leave room for one or two.
Providing for a few more objects than you initially need can save you much
unnecessary work later. If you specify unreasonably large limits, however, you cause
the PATHMON process to allocate unused virtual storage and its corresponding swap-
file space.
For more information about limits and default values, see Appendix C, Configuration
Limits and Defaults. Note that identifying a truly optimum configuration for objects
configured under the Pathway/iTS product can require a significant degree of
calculation and tuning that is beyond the scope of this manual. For additional help,
contact your service provider for details about performance classes offered and for a
description of services available.
Specifying Node Independence
Using the NODEINDEPENDENT attribute of the SET PATHWAY command makes
unspecified node names for processes and devices (for both TS/MP and Pathway/iTS
objects) default to the node where the PATHMON process is running. Using this
attribute in your PATHMON configuration facilitates switching your Pathway application
to another node, either in the event of failure or as part of a planned migration (for
example, in a configuration that includes Nomadic Disk technology). When the
PATHMON process is cool started on the new node, the unspecified node names are
replaced by the name of that node, thereby migrating the associated objects.
If you do not specify a node name as part of the file name for a process or device in a
configuration parameter, the default node for file-name expansion is affected by any
values you specify for the TS/MP CMDVOL command or for the NODEINDEPENDENT
attribute of the TS/MP SET PATHWAY command. The node name used is the node on
which the PATHMON process is currently running if any one of these situations
applies:
•
You set the NODEINDEPENDENT attribute of the TS/MP SET PATHWAY
command to ON and you omit the node name in the parameter
•
You set the node name to \* in a CMDVOL command and you omit the node name
in the parameter
•
You specify \* for the node name in the parameter
For further general information about node independence, see the TS/MP System
Management Manual. For specific information about migrating Pathway/iTS device
names to a new node, see Section 4, Maintaining Pathway/iTS Objects.