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

Maintaining Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
4-25
Migrating Pathway/iTS Objects to a Different System
You can direct these messages to selected users (addressing their terminals by TERM
object name), or to all users accessing your application. Devices represented by both
configured TERM objects and temporary TERM objects can receive these messages.
For example, the following command sends a message about an orientation meeting to
a new user sitting at the device configured through TERM-06:
= TELL TERM TERM-06, "New Employee Orientation at 1:00 p.m."
The next command sends a message about a planned computer system upgrade to all
users of your application:
= TELL TERM *, "Two New CPUs to be Added Tonight!"
In response to the TELL command, the PATHMON process assigns your message a
unique identifying number and queues the message for delivery.
Your message does not interrupt the receiving user’s normal operation at the input-
output device or process; it is not displayed until the user completes interaction with
the current screen. Furthermore, this message can only be displayed if the message
display capability is enabled in the screen program run for the device or process.
The PATHMON process automatically deletes a message when all destination TERM
objects acknowledge its receipt.
You can display the message number and text of all pending messages by entering:
= INFO TELL *
The TELL message number assigned by the PATHMON process enables you to see
the message in specific commands. You will need to use this number, for instance, to
delete TELL message text through PATHCOM. You can delete any individual pending
message by using the DELETE command followed by the message number, for
example:
= DELETE TELL 26
The DELETE command cancels delivery of a pending message. You cannot, however,
issue a global DELETE command that removes all pending messages.
Migrating Pathway/iTS Objects to a Different
System
Careful preparation is required to switch objects in a PATHMON environment to a
different system, either in the event of failure or as part of a planned migration.
The TS/MP System Management Manual provides general considerations for
migrating an entire PATHMON environment to a different system. The node
independence feature of the PATHMON process, described in that manual, provides
assistance for such migrations.
The following paragraphs provide information specific to migrating Pathway/iTS objects
to a different system.