OSI/AS Configuration and Management Manual

Management Environment

OSI/AS Configuration and Management Manual—424119-001

2-17

PROCESS Objects

PROCESS objects identify processes within OSI/AS or within one of its supporting

subsystems. By using SCF commands with PROCESS objects, you can add protocol

processes to or delete them from your subsystem, you can get information on various

processes, or you can change the state of certain subsystem processes. PROCESS

objects allow you to control the OSI manager process and also allow you various levels

of control over NSP, TSP, and TAPS processes.

Process States

During the life of an OSI/AS subsystem process, the process is characterized by a

sequence of states. You can use the SCF STATUS command to inquire about the current

state of the OSI manager process, or of a TAPS or TSP process. Other SCF commands

allow you to change the state of OSI/AS subsystem processes. Figure 2-3 uses boxes to

represent stable process states and arrows to represent transition process states, as they

are reported by SCF commands for OSI/AS.

STARTED means that the process is running and is ready to accept requests from other

subsystem components. This state results from the START command. With NSP

processes, each has an associated LINE object, defined to the underlying Network Layer

subsystem, that must be in the STARTED state before the NSP process can be used as

part of the OSI/AS subsystem. When you use SCF to ask the OSI manager process for

the status of an NSP process, the OSI manager process reports the state of the associated

LINE object. You start NSP LINE objects independently of the OSI manager process.

STOPPED means that the process does not accept requests from other subsystem

components. This state results from the STOP command. When you stop or abort a

TAPS process, a TSP process, or the OSI manager process, the process stops running

(that is, the corresponding Guardian process disappears). However, if a TAPS or TSP

process is not running but is configured to the OSI manager process, SCF reports it as

STOPPED. With NSP processes, an SCF STATUS command reports the state of the

associated line. You stop NSP LINE objects independently of the OSI manager process.

Figure 2-3. Process States

023CDT .CDD

Undefined

Suspended Started

Stopped

Suspending

Starting

Aborting

Stopping

Aborting

Stopping

Suspending