Controlling data definition by object name
You can register object names in the object registration table (ORT) as a way to control data definition. You need to control data definition by object names if you want all objects in the subsystem to be registered and if you want some applications to control specific sets of objects.
About this task
When you control data definition by object name, all objects are registered regardless of whether they are controlled by specific applications.
Procedure
To control data definition by object name:
Example
- Two storage groups (STOG1 and STOG2) and a database (DATB1) that are not controlled by a specific application. These objects can be created, altered, or dropped by a user with the appropriate authority by using any application, such as SPUFI or QMF.
- Two table spaces (TBSP1 and TBSP2) that are not controlled by a specific application. Their names are qualified by the name of the database in which they reside (DATB1).
- Three objects (OBJ1, OBJ2, and OBJ3) whose names are qualified by the authorization IDs of their owners. Those objects might be tables, views, indexes, synonyms, or aliases. Data definition statements for OBJ1 and OBJ2 can be issued only through the application plan named PLANX. Data definition statements for OBJ3 can be issued only through the package collection named PACKX.
- Objects that match the qualifier pattern E%D and the name OBJ4 can be created, altered, or deleted by application plan SPUFI. For example, the objects EDWARD.OBJ4, ED.OBJ4, and EBHARD.OBJ4, can be created, altered, or deleted by application plan SPUFI. Entry E%D in the QUALIFIER column represents all three objects.
- Objects with names that begin with TRULY.MY_, where the underscore character is actually part of the name. Assuming that you specify # as the escape character, all of the objects with this name pattern can be created, altered, or dropped only by plans with names that begin with TRULY.
| QUALIFIER | NAME | TYPE | APPLMATCHREQ | APPLIDENT | APPLIDENTTYPE |
|---|---|---|---|---|---|
| STOG1 | S | N | |||
| STOG2 | S | N | |||
| DATB1 | D | N | |||
| DATB1 | TBSP1 | T | N | ||
| DATB1 | TBSP2 | T | N | ||
| KIM | OBJ1 | C | Y | PLANX | P |
| FENG | OBJ2 | C | Y | PLANX | P |
| QUENTIN | OBJ3 | C | Y | PACKX | C |
| E%D | OBJ4 | C | Y | SPUFI | P |
| TRULY | MY#_% | C | Y | TRULY% | P |
Assume the following installation option:
3 REQUIRE FULL NAMES ===> YESThe entries do not specify incomplete names. Hence, objects that are not represented in the table cannot be created in the subsystem, except by an ID with installation SYSADM authority.