Echelon OpenLNS - Manual (Page 874)

OpenLNS Programmer's Reference 837
The Subsystems collection accessed through the ALL subsystem contains all objects in the
network database, including the subsystems in the system that are managed by the LNS
client applications. This includes transient objects that OpenLNS uses that should not be
accessed by client applications. In general, you should not use the ALL subsystem.
The following table summarizes the Subsystems object.
Description A collection of Subsystem objects.
Added to API Prior to LNS Release 3.0.
Accessed Through AppDevice object.
Router object.
Subsystem object.
System object.
Default Property Item
Methods • Add
• ItemByHandle
• Remove
Properties • ClassId
• Count
• Item
• Parent
• _NewEnum
Methods
The Subsystems object contains the following methods .
• Add
• ItemByHandle
• Remove
Add
Summary Defines a new Subsystem object. A subsystem is an object
that contains other subsystems, application devices, and
routers.
A subsystem is an object that contains other subsystems,
application devices, and routers. Subsystems can be used to
organize devices just as directories can be used to organize
files. For example, each subsystem could represent
groupings of devices in a room, or on a single floor of a
building.
For more detailed information about subsystems and how
they fit into the OpenLNS Object Hierarchy, see the
OpenLNS Object Server Hierarchy section in the OpenLNS
Programmer’s Guide.
Availability Local, full, and lightweight clients.