Securing Application Dictionary Resources › Compiler Security Within the Dictionary › Checking Registration Override Security

Checking Registration Override Security

When Compilers Check Registration Override

The schema and subschema compilers check registration override security when they encounter a SET OPTIONS statement containing a REGISTRATION OVERRIDE clause.

Turned on by REGISTRATION OVERRIDE

Unlike the other kinds of security, this one cannot be turned on or off; that is, the compiler always checks for an authorized user when it encounters a REGISTRATION OVERRIDE clause.

How the Compilers Check the User

To determine who is issuing the REGISTRATION OVERRIDE clause, the compiler looks at user names specified in the user-specification clause of the SET OPTIONS statement. If the SET OPTIONS statement does not include this clause, the user name defaults as described in the SET OPTIONS statement.

Note: For more information about the SET OPTIONS statement, see the CA IDMS Database Administration Guide.

Description of an Authorized User

An authorized user for the REGISTRATION OVERRIDE clause is one who has been defined in the dictionary and whose description includes all authorities. All authorities are assigned through the following IDD DDDL USER statement (use MODIFY for existing user descriptions):

ADD USER NAME IS user-id
    AUTHORITY IS ALL.