Patterns for object sets

When resolving an object set to produce a list of objects, DASD MANAGER PLUS expands each specification and applies the resulting object set in the order that you define.

You can use the same object set for different types of objects. You can resolve the object set for table spaces, indexes, and storage groups, or a mixture of table spaces and indexes. For example, if you resolve the storage group (SG) pattern SG ABC% for table spaces for utility operations, you can then use TS and IX (a mixed list) to include table spaces and indexes but exclude specific indexes.

Related Topics

Using object sets

Creating-dynamic-SQL-object-sets

DASD MANAGER PLUS supports the types of object patterns as shown in the following table:

Pattern Type	Description	File formats
IS	Index space pattern	DBNAME.SPNAME
IX	Index name pattern	CREATOR.IXNAME
OS	DASD MANAGER PLUS object set name	CREATOR.OBJSET
PG	Package name pattern	COLLECTIONID.PACKAGE
PL	Plan name pattern	PLAN (one-part name) CREATOR.PLAN (two-part name)
SG	Storage group name pattern	STOGROUP (one-part name) CREATOR.STOGROUP (two-part name)
SQ	Dynamic SQL statement	Blank
TB	Table name pattern	CREATOR.TBNAME
TS	Table space name pattern	DBNAME.TSNAME (two-part name) DBNAME.TSNAME.CREATOR (three-part name)

Important

If you specify OS in the Obj Type field of the Set Specification panel, DASD MANAGER PLUS ignores the specification fields to the right of the Name or Name Pattern field. Therefore, you cannot use the By Part, Begin Part, End Part, Include IX, Include RI , Include LOB, Include XML, Include HST, and Include ACH fields to further qualify an object set.

For detailed information about using type SQ, see Creating-dynamic-SQL-object-sets.

The following table describes the result set for each pattern type and resolution type. DASD MANAGER PLUS defaults to resolving both table spaces and indexes unless the panel selection or batch syntax indicates a resolution type.

Important

Object sets will not return any table spaces or indexes for objects that are not defined in the catalog. To ensure good performance when specifying which objects to exclude from an object set, you should not add excludes for any objects that are not defined in the catalog.

Resulting object sets for pattern and resolution types

Pattern type	Resolution type	Result set
IS	TS	No match
	IX	Indexes that DBNAME and SPNAME identify
	SG	Storage groups that contain indexes that DBNAME and SPNAME identify
	Blank	Indexes that DBNAME and SPNAME identify
IX	TS	No match
	IX	Indexes that CREATOR and IXNAME identify
	SG	Storage groups that contain indexes that CREATOR and IXNAME identify
	Blank	Indexes that CREATOR and IXNAME identify
OS	TS	Tables spaces that resolve from processing the specifications within the DASD MANAGER PLUS object set
	IX	Indexes that resolve from processing the specifications within the DASD MANAGER PLUS object set
	SG	Storage groups that resolve from processing the specifications within the DASD MANAGER PLUS object set
	Blank	Table spaces and indexes that resolve from processing the specifications within the DASD MANAGER PLUS object set and indexes for resulting table spaces if Include IX is Yes
PG	TS	Table spaces that are referenced within the packages that COLLID and PGNAME identify
	IX	Indexes that are referenced within the packages that COLLID and PGNAME identify
	SG	Storage groups that contain table spaces or indexes referenced within the packages (that COLLID and PGNAME identify) Storage groups for the indexes on the table spaces if Include IX is Yes
	Blank	Table spaces and indexes that are referenced within the packages (that COLLID and PGNAME identify). If Include IX is Yes, the command also includes indexes that are referenced by the resulting table spaces.
PL	TS	Table spaces that are referenced within the plans that PLNAME and CREATOR identify. If the plan contains packages, the plan also includes the table spaces that are referenced within the packages (current or last version).
	IX	Indexes that are referenced within the plans that PLNAME and CREATOR identify. If the plan contains packages, the plan also includes the indexes that are referenced within the packages (current or last version).
	SG	Storage groups that contain table spaces (tables) or indexes referenced within the plans (that PLNAME and CREATOR identify) Indexes on the table spaces if Include IX is Yes
	Blank	Table spaces and indexes that are referenced within the plans that PLNAME and CREATOR identify. If the plan contains packages, the plan also includes the table spaces and indexes that are referenced within the packages (current or last version). If Include IX is Yes, it also includes indexes on the resulting table spaces.
SG	TS	Table spaces using the STOGROUP
	IX	Indexes using the STOGROUP
	SG	Storage groups that CREATOR and STOGROUP identify
	Blank	Table spaces and indexes using the STOGROUP and indexes for resulting table spaces if Include IX is Yes
SQ	TS	Tables spaces (type TS is the first variable) that the SQL execution returns Table spaces using the storage group (type SG is the first variable) that the SQL execution returns
	IX	Indexes (type IX is the first variable) that the SQL execution returns Indexes using the storage group (type SG is the first variable) that the SQL execution returns
	SG	Storage groups that contain the table spaces (TS) and indexes (IX) that the SQL execution returns for types TS and IX Storage groups (type SG is the first variable) that the SQL execution returns
	Blank	Table spaces and indexes that executing the SQL execution returns Table spaces and indexes using the storage group (type SG is the first variable) that the SQL execution returns Indexes on the resulting table spaces if Include IX is Yes
TB	TS	Table spaces that contain tables that CREATOR and TBNAME identify
	IX	Indexes that are defined on tables that CREATOR and TBNAME identify
	SG	Storage groups that contain table spaces in which the tables that CREATOR and TBNAME identify are defined All indexes on the Table spaces if Include IX is Yes
	Blank	Table spaces that contain the tables that CREATOR and TBNAME identify, and the indexes on these tables All indexes on the resulting table spaces if Include IX is Yes.
TS	TS	Table spaces that the DBNAME, TSNAME, and CREATOR identify
	IX	Indexes defined on table spaces that DBNAME, TSNAME, and CREATOR identify
	SG	Storage groups that contain table spaces that DBNAME, TSNAME, and CREATOR identify and their indexes if Include IX is Yes
	Blank	Table spaces with DBNAME, TSNAME, and CREATOR and indexes on those tables if Include IX is Yes

If you set Include RI to Y, DASD MANAGER PLUS uses the table spaces in the result set to locate all referentially related table spaces. If you also specify Include IX Y, DASD MANAGER PLUS includes indexes for RI-added objects in the result set.

For better performance, if you plan to use the object set only for DASD MANAGER PLUS batch programs and plan always to include all indexes, do not set Include IX in each specification. Instead, use INDEX Y in the syntax. Similarly, if you always want to include RI for each specification, use TABLESPACESET in the syntax and RI N in object set specifications. However, if you need the set for online generation or more granular control, use the object set specification method.

Patterns for object sets

On this page