OSI/AS Management Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

Data Communications Standard Definitions

Common Definitions

056785 Tandem Computers Incorporated 4–9

The indirect-process-name identifies a TAPS, TSP, or NSP process through its associated

OSI manager process. This format is allowed only in commands directed to the OSI

manager process—that is, commands in which the value of either ZSPI-TKN-

MANAGER or ZCOM-TKN-XMGR is the name of the OSI manager process.

The

object-name

for the PROCESS object for

indirect-process-name

has the

following format:

osi-mgr-name

process-type.internal-name

osi-mgr-name

is the Guardian 90 process name of the OSI manager process that manages the

specified TAPS, TSP, or NSP process.

process-type

is #TAPS, #TSP, or #NSP, denoting a TAPS, TSP, or NSP process.

internal-name

is the name by which the specified process is known to the OSI manager process.

It is a string of up to eight alphanumeric characters, the first of which must be

alphabetic.

#process-type.internal-name together must be a unique name. For example,

#NSP.A1 and #TSP.B1 are valid combinations.

Wild-Card Support

Wild cards are supported for the ABORT PROCESS, ACTIVATE PROCESS,

ALLOWOPENS PROCESS, DELETE PROCESS, FORBIDOPENS PROCESS, INFO

PROCESS, LISTOBJECTS PROCESS, START PROCESS, STATUS PROCESS, STOP

PROCESS, and SUSPEND PROCESS commands. You can specify wild cards in the

#process-type

internal-name

fields. Examples of the

#process-type

and

internal-name

fields with wild cards are:

.*.E*

.#*.E*

.#TA*.*

.#NSP.N*

.#TSP.*1

Examples

$OSIM.#TAPS.TAPS1

$OSIM.#TAPS.TAPS*

$OSIM.#NSP.X251

$OSIM.#TSP.TSP1

$OSIM.#TSP.TSP1?