OSI/AS Management Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Data Communications Standard Definitions

Common Definitions

4–8 056785 Tandem Computers Incorporated

For the LISTOBJECTS command, no object name is specified for the null object type.

For the GETVERSION command, if an object name is specified, it must be of the form:

process-name

is the Guardian 90 process name of an OSI manager or TAPS process.

Wild-Card Support

Wild cards are not supported for the null object.

ZCOM-OBJ-PROCESS

A PROCESS object identifies a specific process. Use the PROCESS object to define

processes that provide data-communications and subsystem-management services.

Four kinds of PROCESS objects can be specified:

Tandem application, presentation, and session service provider (TAPS) processes,

Transport service provider (TSP) processes,

Network service provider (NSP) processes, and the

OSI manager process.

Note that only TAPS processes and the OSI manager process are part of the OSI/AS

subsystem; TSP and NSP processes belong to lower-level subsystems that are used by

the OSI/AS subsystem.

This manual describes only operations supported by the TAPS processes and the OSI

manager process. This support includes a full range of operations on TAPS processes

and on the OSI manager process itself, a more limited number of operations on TSP

processes, and a minimal set of operations on NSP processes.

The

object-name

for the PROCESS object can be either

indirect-process-name

process-name

(these are described on the next page). When you use

indirect-

process-name

, the command is directed through the OSI manager process first, then

on to the specified process. The OSI manager process updates the MIB accordingly. If

you use

process-name

, the command bypasses the OSI manager process (the MIB

will not be updated) SCP passes the command directly to the appropriate subsystem

(OSI/AS for TAPS processes, OSI/TS for TSP processes, and X25AM or TLAM for

NSP processes), and the command must follow the rules for that subsystem rather

than those described in this manual. The programmatic commands acceptable to

OSI/TS, X25AM, and TLAM are described in the management programming manuals

for those subsystems.

You must use

process-name

in commands that operate on the OSI manager process.

When both name formats are available, it is preferable to use

indirect-process-

name