OSI/AS Management Programming Manual

Data Communications Standard Definitions
Common Definitions
056785 Tandem Computers Incorporated 4–11
Examples
$MGR.#L5.REMOTE1
$MGR.#L5.REMOTE*
$MGR.#L4.LOCAL1
$MGR.#L3.REMOTE2
$MGR.#L?.REMOTE2
ZCOM-OBJ-SERVICE
ZCOM-OBJ-SERVICE defines attributes to be associated with a specific service
element or protocol layer. Names of SERVICE objects have the following form:
$ process-name .# service-name
$ process-name
is the Guardian 90 process name of the OSI manager process or TAPS process
associated with the specified SERVICE object.
# service-name
is #L3, #L4, #L5, #L6, or #ACSE, denoting a Layer 3, Layer 4, Layer 5, Layer 6, or
ACSE SERVICE. Only #L5, L6, and #ACSE are valid if $ process-name is a
TAPS process.
Wild-Card Support
Wild cards are supported for the INFO SERVICE, LISTOBJECTS SERVICE , and
STATISTICS SERVICE commands, You can only specify wild cards in the service-
name field. Examples of the service-name field with wild cards are:
.*
.#*
.#?
.#L*
Examples
$TAP1.#ACSE
$TAP2.#L6
$TAP1.#L5
ZCOM-OBJ-SU
ZCOM-OBJ-SU defines a subdevice subordinate to a TAPS process. There are two
types of SUs: static and dynamic. A static SU object is temporary, it is added
dynamically by the OSI manager process and lasts only as long as the connection
exists. A dynamic SU object is saved when the connection is finished and can be
reused by another connection if that connection desires the same addresses and