TS/MP 2.5 System Management Manual

There is an interval when the PATHMON process can grant a link to an associative server process
that is stopping itself. Although the stopped state allows you to use the ALTER SERVER command
to specify changes for configuration attributes, the changes you specify do not take effect until the
associative server is actually stopped and then restarted from the same the PATHMON process.
Changes to these attributes do not take effect until the PATHMON process receives a START
SERVER command for an associative server that has actually stopped:
PRIOUTASSIGN
PROGRAMOWNERDEFINE
SECURITYVOLUMEGUARDIAN-LIB
STARTUPPARAMHOMETERM
IN
Associative Servers as Subtype 30 Processes
An associative server can be a subtype 30 process, which simulates a terminal or communication
device. When an associative server is a subtype 30 process, the PATHMON process determines
the server’s device type; you do not have to designate the device type with the TYPE option of the
RUN PROGRAM command. This configuration is typical when a server process acts as a front end
process (fep) for a terminal. High-level language support (HLS) is often configured this way.
Migrating Your Environment to a Different System
Careful preparation is required to switch your PATHMON environment to a different system, either
in the event of failure or as part of a planned migration.
The best preparation for any such move is to anticipate it when you first configure your PATHMON
environment. When you set global attributes using the SET PATHWAY command, set the
NODEINDEPENDENT attribute to ON to make unspecified node names for processes and devices
default to the node where the PATHMON process is running after cool start. By configuring your
application for node independence and then leaving the node unspecified in any name you
configure, you can avoid much of the work involved in renaming objects and processes configured
with hard-coded node names. For more information on configuring your system for
node-independence, see “Specifying Node Independence” (page 54) and “SET PATHWAY
Command” (page 159). The SET PATHWAY syntax description includes a list of objects and attributes
that are node-independent when the NODEINDEPENDENT attribute is set to ON.
Even with a node-independent PATHMON environment, a number of migration considerations
arise. The node-independent designation can provide a smooth migration for disk files and process
names. However, you might have to change parts of device names manually even if the node
portion of the name is independent. For example, if you are migrating terminals or printers, you
will either need to manually change the device names or ensure that terminal and printer devices
with the same names are attached to the new node. Other attributes need careful review as well—for
example, processor and user ID specifications. This table lists object attributes that you might have
to change with the ALTER command when migrating your application. The table includes objects
supported by the NonStop TS/MP product and, as noted, the Pathway/iTS product.
Table 3 Migration Considerations: Object Attribute Values
Considerations/ RecommendationsAttributeObject or Process
Ensure that CPUs on new system have same
numbers or change manually.
BACKUPCPU cpu-numPATHMON process
Specify a new DUMP file name if the name
was previously specified.
DUMP ON | OFF
Ensure that user ID is known to new system
or change manually.
OWNER owner-idPATHWAY object
106 Maintaining a PATHMON Environment