Controlling data definition by application name with exceptions

You can register an application name with exceptions in the application registration table (ART) as a way to control data definition.

Procedure

To control data definition by application name with exceptions:

  1. Choose not to control all applications.
    On the DSNTIPZ installation panel, specify the following value for option 2: 
    2 CONTROL ALL APPLICATIONS ===> NO
    When you specify NO, you allow unregistered applications to use data definition statements on some objects.
  2. On the DSNTIPZ installation panel, specify the following for option 4: 
    4 UNREGISTERED DDL DEFAULT ===> APPL
    When you specify APPL, you restrict the use of data definition statements for objects that are not registered in the ORT. If an object is registered in the ORT, any applications that are not registered in the ART can use data definition language on the object. However, if an object is not registered in the ORT, only applications that are registered in the ART can use data definition language on the object.
  3. In the ART, register package collections and plans that you will allow to issue data definition statements on any object. Enter the value Y in the DEFAULTAPPL column for these package collections. Applications that are registered in the ART retain almost total control over data definition. Objects that are registered in the ORT are the only exceptions.
  4. In the ORT, register all objects that are exceptions to the subsystem data definition control that you defined in the ART. You must supply values for the QUALIFIER, NAME, TYPE, APPLMATCHREQ, APPLIDENT, and APPLIDENTTYPE columns of the ORT. You can enter information in other columns of the ORT for your own use.

Example

Suppose that you want almost all of the data definition language in your subsystem to be issued only through an application plan (PLANA) and a package collection (PACKB).
Table 1. Table DSN_REGISTER_APPL for total subsystem control with exceptions
APPLIDENT APPLIDENTTYPE DEFAULTAPPL
PLANA P Y
PACKB C Y

However, suppose that you also want the following specific exceptions:

  • Object KIM.VIEW1 can be created, altered, or dropped by the application plan PLANC.
  • Object BOB.ALIAS can be created, altered, or dropped only by the package collection PACKD.
  • Object FENG.TABLE2 can be created, altered, or dropped by any plan or package collection.
  • Objects with names that begin with SPIFFY.MSTR and exactly one following character can be created, altered, or dropped by any plan that matches the name pattern TRULY%. For example, the plan TRULYJKL can create, alter, or drop the object SPIFFY.MSTRA.

The following table shows the entries that are needed to register these exceptions in the ORT.

Table 2. Table DSN_REGISTER_OBJT for subsystem control with exceptions
QUALIFIER NAME TYPE APPLMATCHREQ APPLIDENT APPLIDENTTYPE
KIM VIEW1 C Y PLANC P
BOB ALIAS C Y PACKD C
FENG TABLE2 C N    
SPIFFY MSTR_ C Y TRULY% P

You can register objects in the ORT individually, or you can register sets of objects.