OSI/AS Configuration and Management Manual

Management Environment

OSI/AS Configuration and Management Manual—424119-001

2-20

Types of PROCESS Objects

OSI/AS defines three different types of PROCESS objects. Each of these types has an

associated type identifier that you must use in SCF commands to identify the process

you want to manage. Table 2-3

shows each PROCESS object type identifier.

Naming PROCESS Objects

There are two naming conventions for PROCESS objects within the OSI/AS subsystem,

as follows:

1. indirect-process-name identifies a PROCESS object indirectly through the

OSI manager process. For example, a sensitive command using TSP

indirect-process-name acts on the TSP process, but is routed to that process

by the OSI manager process; any changes in the process are, therefore, registered in

the MIB.

indirect-process-name consists of three parts:

•

Name of the OSI manager process that controls the subsystem

•

Type to which the PROCESS object belongs

•

String that identifies the PROCESS object uniquely

indirect-process-name has the following format:

Here are three examples that illustrate this syntax:

$OSIM.#NSP.X25A

$OSIM.#TSP.TSP1

$OSIM.#TAPS.TAPS1

2. process-name identifies a PROCESS object directly, bypassing the OSI manager

process. For example, a sensitive command using TSP process-name acts

directly on the TSP process and is not registered by the OSI manager process in the

MIB.

The PROCESS object name is specified in the usual form for Guardian process

names. (If the process runs on a network node other than your own, you must add

the name of the system in which the process runs. See the OSI/AS SCF Reference

Manual for more details.) process-name identifies the process uniquely within

the subsystem.

Table 2-3. Type Identifiers for PROCESS Objects

Type Identifier Description

NSP Network service provider

TSP Transport service provider

TAPS Application, presentation, and session service provider

$osi-mgr-name.#process-type.internal-name