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

Configuring Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
2-14
Communication Between PATHMON Environments
Configuring a Template for Several Device Types
A PROGRAM object can serve as a template for several device types. The template
can optionally associate several device-related attributes with each device type. These
attributes include the initial screen program for that device type, the printers associated
with the device type, and the ability of the device type to accept the BREAK key
function and to echo input characters on the screen. This template can be used over
and over again to start many devices of the specified type or types. Through the
PROGRAM, any device of the appropriate type can access the application.
Specifying Security for a PROGRAM Object
You can specify security for a PROGRAM object by setting the OWNER and
SECURITY attributes of the SET PROGRAM command. The OWNER attribute
specifies the owner of the current PROGRAM object. The owner can alter the security
attribute for the PROGRAM object. The SECURITY attribute (A, G, O, -, N, C, or U)
values are the same as those for Guardian operating environment security attributes.
The SECURITY attribute specifies who can run the PROGRAM object.
The following example specifies that only the owner—user ID 8,61—can run this
PROGRAM object:
= SET PROGRAM OWNER 8,61
= SET PROGRAM SECURITY "O"
The next example specifies that any local or remote user can run the PROGRAM
object:
= SET PROGRAM OWNER 8,61
= SET PROGRAM SECURITY "N"
Communication Between PATHMON
Environments
When one PATHMON environment communicates with another, the PATHMON
process for each environment controls and reports on its own objects. When a TCP in
one PATHMON environment executes a screen program request directed to a server
class controlled by another PATHMON process, these operations occur:
1. The TCP requests a link from the external PATHMON process that controls the
server class.
2. The external PATHMON process grants the link to the server process.
3. The TCP uses the link to open the remote server process and send the request to
that server process.
4. After the remote server process completes its work, it returns its reply to the TCP.
The same general operations take place whether the PATHMON environments are
running on the same or on different nodes.