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

Maintaining Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
4-26
Migrating Pathway/iTS Objects to a Different System
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, CPU and user ID specifications. Table 4-1 lists Pathway/iTS object attributes
that might need to be changed with the ALTER command when migrating your
application.
Table 4-1. Migration Considerations: Pathway/iTS Object Attribute Values
Object or Process Attribute
Considerations/
Recommendations
TCP CPUS
pricpu:backupcpu
Make sure that CPUs on
new system have same
numbers or change
manually
HOMETERM termname Make sure that a terminal
with same name exists on
new system or change
manually
TERM FILE filename Make sure that a device
with same name exists on
new system or change
manually
PROGRAM OWNER owner-id Make sure that user ID is
known to new system or
change manually
PRINTER filename Make sure that a device
with same name exists on
new system or change
manually
Note. The SWAP and GUARDIAN-SWAP attributes are not included in Table 4-1 because
TCP swap space is now handled by the Kernel-Managed Swap Facility (KMSF) and the SWAP
and GUARDIAN-SWAP values are no longer used. However, if you do specify device names
for these attributes, you must ensure that the named devices exist; otherwise, an error occurs.
In a node-independent environment, it is recommended that you do not specify values for these
attributes.