Pathway/XM System Management Manual

Configuring the Pathway/XM Environment
Compaq NonStop™ Pathway/XM System Management Manual—426761-001
4-20
Configuring Object Attributes for Future Migration
You should also consider whether your SCREEN COBOL or Pathsend requesters—
perhaps those running on remote systems—use hard-coded system, volume, or
subvolume names in requests to server processes that belong to the application you want
to migrate. If Pathsend procedure calls or screen application requests use such hard-
coded names, the applicable code might need to be changed manually.
PARAM param-string Could include system name stored as
buffer; check and change manually if
required.
STARTUP startup-
string
Could include system name stored as
buffer; check and change manually if
required.
VOLUME $volume Ensure that volume is known to new
system or change manually.
System name might be passed in
startup message; check and change
manually if required.
SERVER process GUARDIAN-SWAP
$volume (for
NonStop
TM
TS/MP
versions earlier than D42)
Ensure that a disk attached to new
system has same name or change
manually.
HOMETERM termname Ensure that a terminal with same
name exists on new system or change
manually.
TCP template HOMETERM termname Ensure that a terminal with same
name exists on new system or change
manually.
TCLPROG Ensure that volume portion of the file
name is known to new system or
change manually.
TERM object FILE filename Ensure that a device with same name
exists on new system or change
manually.
PROGRAM object OWNER owner-id Ensure that user ID is known to new
system or change manually.
PRINTER filename Ensure that a device with same name
exists on new system or change
manually.
Table 4-1. Migration Considerations: Object Attribute Values (page 2 of 2)
Object or Process Attribute Considerations/ Recommendations