Specifying objects for a new object set
You can specify objects for a new object set in a number of ways, depending on your situation or application, as follows:
Method | Description | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Table space and/or Owner | Specify a table space name (databaseName.tableSpaceName) or pattern to create the object set. This method is usually the fastest way to produce an object set of table spaces and associated indexes. Optionally, you can specify the owner in the pattern. The default value is an * (asterisk). You can manipulate the list to exclude or add additional spaces. You can also include one or more partitions when working with partitioned table spaces. You can optionally include objects associated with the objects included in the object set, as follows:
| ||||||||||||||||||||
Table name | Specify a table name (creator.tableName) or pattern to create the object set. You can manipulate the list to exclude or add additional tables. You can optionally include objects associated with the objects included in the object set, as follows:
| ||||||||||||||||||||
Index | Specify an index name (authID.indexName) or pattern to create the object set. When you specify the indexes, you can also optionally list one or all partitions of the index. | ||||||||||||||||||||
Volume | Specify up to eight volumes concurrently by using the operating system volume names. You cannot use wildcards to specify a object set of volumes. For more information, see Creating-volume-based-object-sets. | ||||||||||||||||||||
STOGROUP | Specify objects by storage object set name or pattern to create the object set. | ||||||||||||||||||||
Plan | Specify objects by plan name or pattern to create the object set. When running on Db2 Version 10 or later, BMC AMI Recovery Manager will include objects with package dependencies for object sets built by plan name. These restrictions do not apply to Repository plan object sets. | ||||||||||||||||||||
Package | Specify objects by package (collectionID.package) to create the object set. | ||||||||||||||||||||
Exception status | Specify objects by exception status to create the object set. You can also choose to include all objects in one or more status types, all objects that are related by referential integrity, and all indexes on those objects. The status types that you can choose from are:
| ||||||||||||||||||||
Dynamic SQL | Specify objects by using a user-defined SQL SELECT statement. The SQL statements must be exactly as shown in the examples in the following table and cannot deviate except in the WHERE clause.
Specify TS, IX, or SG as the first variable. BMC AMI Recovery Manager checks to make sure that 'TS', 'IX', or 'SG' follows the SELECT statement. Only one SQL statement is accepted. The statement is limited to 16,000 characters. Semicolons are not allowed. If not specified, the partition number is set to 0. The IX name length and number of partitions follow the rules of the Db2 Version that you are using. Letters are used to represent related objects in the online Recovery Definition display and ARMBGRP Definition report. The following table provides the letters used and their definitions. While BMC’s Recovery Management products can resolve all of these letters designations, BMC AMI Recovery Manager can create only Y (Yes) and N (No). Only DASD MANAGER PLUS version 11.1.00 and later can create B (Bases only) and O (Only this type), in addition to creating Y (Yes) and N (No).
For examples, see Sample-ARMBGRP-JCL-and-output. | ||||||||||||||||||||
Recovery object sets | For ARMBGPS size balancing for a subset of the Db2 subsystem, specify the include and exclude patterns with the table space name or pattern to create the object set. These object sets are referred to as ARMBGPS application object sets and simplify the method for generating multiple jobs for an application. (These object sets are TYPE BA in the OBJSETS table.) | ||||||||||||||||||||
Repository plan | Specify an object set of plan names corresponding to the repository plan names for BMC AMI Recovery Manager, BMC AMI Recover, and Log Master. | ||||||||||||||||||||
Object set combination | Specify objects that are contained in other existing object sets to create a new object set. Object sets created via this method simply copy the definitions of the specified existing object sets and do not pull information directly from the catalog and directory. This method provides a way of create a new object set using mixed criteria (for example, storage group name and table space pattern). | ||||||||||||||||||||
Subsystem | Automatically create a set of balanced object sets for an entire Db2 subsystem. For more information, see Full-subsystem-recovery. | ||||||||||||||||||||
Indexspace | Specify an index space name (databaseName.indexSpaceName) or pattern to create the object set. When creating an object set by index space, you can include any number of index space names or wildcard patterns. | ||||||||||||||||||||
Object Sets | Specify a table space name and indexes by object set pattern to create a new object set. When creating an object set you can include wildcard patterns. |
Set specification expansion
Wildcard processing uses the following characters and results in the use of a SQL LIKE operator for expansion:
- * (asterisk) and % (percent sign): matches 0 to any number of characters in an object name string
? (question mark) : matches any single character in an object name string
If the qualifier does not contain any of the characters, BMC AMI Recovery Manager uses an equal operator (=) to locate a match. The qualifier terminates when the first blank encountered.
When the patterns are expanded, all exclude patterns are processed first to build an exclusion list that is then applied to the include patterns, which are processed in order of inclusion.
For more information, see Using-wildcards-when-building-object-sets.
SQL specification
If the pattern type is SQ, you enter a SQL statement. Whenever you enter or update the SQL statement, BMC AMI Recovery Manager performs a SQL PREPARE INTO to verify that the statement is valid.
Related topic