OSI/AS SCF Reference Manual

Introduction
OSI/AS SCF Reference Manual—424121-001
1-2
Object Types
Object Types
Figure 1-1 shows the OSI/AS object types supported by SCF and their hierarchical
order.
As shown, the SUBSYS (subsystem) object is at the highest point of the hierarchy, with
all other objects subordinate to it. (The null object is not an actual object type but is used
in commands that do not require specification of an object type.) Immediately
subordinate to the SUBSYS object are the PROCESS, ENTRY, SERVICE, and
PROFILE objects. PROCESS objects, TAPS processes or Transport Service Provider
TSP processes, can have subordinate SU (subdevice) and SERVICE objects.
The SERVICE object appears in two places in the hierarchy because Layer 5, Layer 6,
and ACSE SERVICE objects can be inquired about either indirectly through the OSI
manager process or directly through their associated TAPS processes. These SERVICE
objects can be altered only through the OSI manager process.
Layer 3 and Layer 4 PROCESS or SERVICE objects can be inquired about and altered
either through the OSI manager process or directly through their associated TSP process.
Figure 1-1. OSI/AS Subsystem Object Hierarchy
010CDT .CDD
PROCESS ENTRY SERVICE
SUBSYS
or
null
PROFILE
For an OSI Manager
Process:
PROCESS
or
null
SERVICE
SU
For a TAPS Process: