TS/MP 2.5 System Management Manual

unspecified, the node name always defaults to the node where the PATHMON process is running
at any given time.
Migration Considerations
Designating your PATHMON application as node-independent simplifies, but does not eliminate,
the tasks associated with migrating an application from one system to another. Migrating device
names configured under Pathway/iTS, for example, is not useful unless physical devices with those
names are connected to the new node. For considerations when migrating your PATHMON
application to a new node, see “Migrating Your Environment to a Different System” (page 106).
Specifying Security
You can specify security for your PATHMON environment by setting the OWNER and SECURITY
attributes of the SET PATHWAY command.
The OWNER attribute indicates the owner of the PATHMON environment, who can stop the
PATHMON process, add programs, delete objects, and so on. The owner can change every
attribute of the global configuration.
PATHMON SECURITY values (A, G, O, -, N, C, and U) are the same as Guardian security values.
This example specifies that only the owner—user ID 8,61—can modify the PATHMON environment:
SET PATHWAY OWNER 8,61
SET PATHWAY SECURITY O
The next example specifies that any member of user group ID 8 can modify the PATHMON
environment:
SET PATHWAY OWNER 8,61
SET PATHWAY SECURITY G
Before you issue the START PATHWAY command, the owner ID is always the process accessor ID
of the PATHMON process and the security attribute is O (owner). This setting prevents alteration
of the global configuration parameters.
NOTE: After you issue the START PATHWAY command, if you do not specify a value for the
security attribute, it defaults to N (any local or remote user). If the owner of this system is the super
ID, the N value results in a security risk for your system. You must set the security attribute to O,
so that only persons logged on as the super ID can add, delete, or modify PATHMON-controlled
objects.
The default security attribute is “O”.
You can also specify security for running programs, as described later in this section.
Configuring PATHMON-Controlled Objects
After specifying global limits and issuing the START command, you configure the SERVER objects
that run under the PATHMON process to support your application.
If your environment includes the Pathway/iTS product, you also configure TCP, TERM, and
PROGRAM objects. For instruction on configuring these objects, see the Pathway/iTS System
Management Manual.
You create and control objects by defining and changing their attributes. PATHCOM maintains a
list of attributes that describe configuration information for each object: how it relates to other
objects and how it must be managed by the PATHMON process. The attributes for a server, for
instance, specify the server name, the server type (Guardian or OSS) the CPUs on which the server
runs, the server’s execution priority, the name of the program the server runs, and other
characteristics.
Configuring PATHMON-Controlled Objects 55