Using dynamic object sets

With dynamic object sets, when an object set is referenced (created, opened, or updated), BMC AMI Recovery Manager returns all of the objects that meet the object set definition at that moment in time. These objects include wildcards for pattern matching in their definitions. (For more information about wildcards, see Set specification expansion.)

You can still create static object sets by defining an object set as a list of individual objects with no wildcards included. The object set attempts to resolve to the same set of objects each time the object set is opened. However, if one or more objects have been dropped, the dropped objects will not be present in the list of objects. Also, object sets that you create based on exception statuses and volume serial numbers (VOLSERs) are created as static object sets.

While the dynamic object sets capability is used at the time of JCL generation, once the JCL is generated, the list of objects in the JCL becomes a static list unless you use the OBJECTSET syntax.

With dynamic object sets, you can create an empty object set (an object set for which no objects are found that meet the definition). After you create the objects and then open the object set, the objects are found and displayed in the object set. This ability enables you to prepare to back up and recover objects that do not yet exist. For example, if you know that a new application is being added to your system, you can set up the object set in advance using wildcards to define the object set. When the objects are created and the object set is opened, BMC AMI Recovery Manager automatically finds the objects for the object set and adds them to the backup and recovery jobs.

This section contains the following topics: