Objects can be selected based on the dependency of other objects on them by using the selection criteria “i”. The dependency implosion criteria uses the set of objects selected so far to select the objects depending on those objects. It takes the set of currently selected objects and performs the implosion operation on that set of objects. The nature and extent of the implosion is determined by attaching further criteria qualifiers. If no qualifier is attached, all objects that the object depends on are added to the set of objects selected. If a “p” is attached, this indicates a program dependency implosion. If followed by a “t”, this indicates an object creation dependency implosion. The “h” option indicates a Hollow implosion process, which results in only the set of imploded objects without the original objects.

Note: Dependencies between objects and dependency implosions are explained in Object Dependencies.

The following command finds all objects depended on by the object “Customers,” and includes the original object as well.

ZOMList Customers +i

Since the dependency implosion depends on having previously selected some objects, the “i” selection operator should never be used as the first selection criteria.

In a hollow dependency implosion, the original set of objects is excluded from the result. The following command finds all objects depended on by objects named “Customers” but excludes the “Customers” objects:

ZOMList Customers +i h

The following command finds all objects depended on by the object “Customers,” and all objects on which they depend, and recurses until no further dependent objects are found. Program references are omitted from the dependency tree imploded.

ZOMList Customers +i t

The following command finds all objects depended on by the object “pMainMenu,” and all objects on which they depend, and recurses until no further dependent objects are found. Program references are used rather than object creation dependencies when the dependency tree is imploded.

ZOMList pMainMenu +i p