OSI/AS Configuration and Management Manual

Management Environment
OSI/AS Configuration and Management Manual—424119-001
2-11
null Objects
Seven types of objects are common to all OSI/AS subsystems:
•
null object
•
ENTRY object
•
PROCESS object
•
PROFILE object
•
SERVICE object
•
SU (subdevice) object
•
SUBSYS (subsystem) object
During the connection-establishment phase, the OSI manager process selects attribute
values from these objects according to a predetermined set of rules. These rules are
discussed in Selection Hierarchy of Object Attributes
on page 2-35.
From the perspective of the OSI manager process, an application entity must identify all
the addresses, profiles, and processes it uses for its OSI connections. The following
subsections explain how you use objects to identify and manage your OSI/AS
subsystem:
null Objects
Null object types are not actual object types, but are in commands that do not require
specification of a particular object type. In OSI/AS, null objects can be used to obtain
version information or to identify all objects supported by the OSI/AS subsystem.
SCF Commands for null Objects
You can use the following SCF commands with the null object:
Examples of Nonsensitive Commands
The following examples show nonsensitive commands that you can use to collect
information on your subsystem:
NAMES $OSIM
NAMES $TAPS
VERSION $TAPS
VERSION $OSIM
VERSION $TSP
VERSION $TSP, DETAIL
NAMES Displays the names of all objects associated with the specified
OSI manager process or the specified TAPS process.
VERSION Displays the version level of the OSI/AS product.