TS/MP System Management Manual (G06.24+, H06.03+)

Maintaining a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
5-36
Migrating Your Environment to a Different System
You should also consider whether Pathsend requesters or SCREEN COBOL
applications —perhaps those controlled by remote systems—use hard-coded node
names in requests to server processes that belong to the application you want to
migrate. If Pathsend procedure calls and screen application requests have not been
coded for node independence, the applicable code must be changed manually.
If you plan to switch your application to a new system, and especially if you plan to
migrate your application on a regular basis, you should consider creating an Command
file to accomplish any required manual changes.
PRINTER filename Ensure that a device with
same name exists on new
system or change manually.
TCL PROG Ensure that volume portion
of the file name is known to
new system or change
manually.
*Objects configured under Pathway/iTS only
Note. The SWAP and GUARDIAN-SWAP attributes are not included in Table 5-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.
Table 5-1. Migration Considerations: Object Attribute Values (page 3 of 3)
Object or Process Attribute
Considerations/
Recommendations