OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-65
PROCESS Objects
process
is the name used to distinguish this PROCESS object from all other objects in this
OSI/MHS subsystem, and in particular from other PROCESS objects. The name
must be an alphabetic character followed by zero through three alphanumeric
characters. In this context, the process name is not preceded by a dollar sign ($),
but it is preceded by a pound sign (#) if the gsystem qualifier is omitted.
You assign process, the qualifying name of the PROCESS object, by means of
an attribute of the group that contains the process:
•
In a GI group, the group attribute GI-PNAME names the GIP.
•
In an LO group, the group attribute LO-PNAME names the LO process.
•
In an MR group:
The group attribute MRP-PNAME names the MR process.
The group attribute RTS-PNAME names the RTS process.
The group attribute SC-PNAME names the SC process.
•
In an MS group, the group attribute MS-PNAME names the MS process.
•
In an RS group, the group attribute RS-PNAME names the RS process.
The value you assign to each of these attributes must be a process-level qualifier
and have no more than four characters.
For example, you could name an MHS manager process running on SYSTEM1
“$ZMHS. ” And an MS group, also running on SYSTEM1, could contain an MS
process named “MSP3. ” Then, to direct a command to this process from inside
SYSTEM1, you would use the name “$ZMHS.#MSP3.”
Note that a complete process name in OSI/MHS lacks a qualifier to identify the type of
process to which commands are to be directed. The commands for PROCESS objects
are all informational; no serious harm can result from the wrong process name in a
command. However, you may waste time trying to remember the name of a process
unless you set up a good naming convention for all your OSI/MHS objects.