OSI/MHS Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

131

132

133

134

135

136

137

138

139

140

Management Environment for OSI/MHS

OSI/MHS Configuration and Management Manual—424827-003

2-63

PROCESS Objects

NAMES MTA $ZMHS.#WASHDC, SUB ALL

NAMES MTA $ZMHS.#NYC05, SUB ONLY

The following command shows the attributes you must include when adding an MTA

object. The last four attributes set a pair of OSI addresses for the object. Up to seven

pairs are possible; at least one pair is required.

ADD MTA $ZMHS.#BOSTON, REM-APPLIC-CONTEXT MTS-TRANSFER, &

REM-MTA-NAME MTA127, ISO-COUNTRY-NAME US, &

REM-ADMD ATT, REM-TSELECTOR-1 4D5258323541, &

REM-NSAP-1 703285003020, &

LOC-TSELECTOR-1 4D5258323541, &

LOC-NSAP-1 703285003011

The remote OSI address of the pair is an address of the adjacent MTA represented by

this MTA object. The local OSI address is an address of this OSI/MHS subsystem.

Note that each address has two parts: TSELECTOR (same as OSI TSEL) and NSAP.

Two is the fewest number of parts ever required for an OSI address in OSI/MHS.

PROCESS Objects

A PROCESS object identifies an OSI/MHS process that is subordinate to a GROUP

object. Groups are of five kinds: GI, LO, MR, MS, and RS. Each group contains a

single process or set of processes.

For manipulation by SCF commands, these processes are identified by the groups to

which they belong. To create or delete a PROCESS object, or to change its state or

attributes, you direct a command to its group.

The SCF commands that affect a PROCESS object directly are all informational

commands. Using the PROCESS object type, you can:

•

Find out the names of some or all processes in the OSI/MHS subsystem

•

Obtain trace records from a process and statistics about its performance

•

Find out the operational status of a process

PROCESS Object States

An OSI/MHS process has a summary state of DEFINED only. You cannot directly

ascertain the state of an OSI/MHS PROCESS object from within the subsystem, but

you can infer it from the summary state of the group that contains the process. See

GROUP Object Summary States on page 2-49 for more information.