Registering object sets

Registering object sets enables you to save time and to simplify object registration.

About this task

Registering object sets is not a data definition control method; you must install of the data definition control methods before you can register any object sets.

Because complete two-part names are not required for every object that is registered in the ORT, you can use incomplete names to register sets of objects. To use incomplete names and register sets of objects, enter option 3 on the DSNTIPZ installation panel as follows: 

3 REQUIRE FULL NAMES       ===> NO

The default value YES requires you to use both parts of the name for each registered object. If you specify the value NO, an incomplete name in the ORT represents a set of objects that all share the same value for one part of a two-part name. Objects that are represented by incomplete names in the ORT require an authorizing entry in the ART.

Example

If you specify NO for option 3, you can include entries with incomplete names in the ORT. The following table shows entries in the ORT for the following objects:
Table 1. Table DSN_REGISTER_OBJT for objects with incomplete names
QUALIFIER NAME TYPE APPLMATCHREQ APPLIDENT APPLIDENTTYPE
  TABA C Y PLANX P
  TABB C Y PACKY C
SYSADM   C N    
DBSYSADM   T N    
USER1 TABLEX C N    
  • Two sets of objects, *.TABA and *.TABB, which are controlled by PLANX and PACKY, respectively. Only PLANX can create, alter, or drop any object whose name is *.TABA. Only PACKY can create, alter, or drop any object whose name is *.TABB. PLANX and PACKY must also be registered in the ART with QUALIFIEROK set to Y, as shown in the following table: That setting allows the applications to use sets of objects that are registered in the ORT with an incomplete name.
    Table 2. Table DSN_REGISTER_APPL for plans that use sets of objects
    APPLIDENT APPLIDENTTYPE DEFAULTAPPL QUALIFIEROK
    PLANA P N Y
    PACKB C N Y
  • Tables, views, indexes, or aliases with names like SYSADM.*.
  • Table spaces with names like DBSYSADM.*; that is, table spaces in database DBSYSADM.
  • Tables with names like USER1.* and tables with names like *.TABLEX.

APPLMATCHREQ=N and objects SYSADM.*, DBSYSADM.*, USER1.*, and *.TABLEX can be created, altered, or dropped by any package collection or application plan. However, the collection or plan that creates, alters, or drops such an object must be registered in the ART with QUALIFIEROK=Y to allow it to use incomplete object names.