Defining a Database Using Non-SQL › Security Checking › Checking Registration Override Security

Checking Registration Override Security

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

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.

Determining Who is Issuing the Statement

To determine who is issuing the REGISTRATION OVERRIDE clause, the compiler looks at the PREPARED BY and REVISED BY user names in the SET OPTIONS statement. If the SET OPTIONS statement does not include either clause, or if user signon override is not allowed, the user name defaults as described in the SET OPTIONS presentation under Chapter 10, “Using the Schema and Subschema Compilers”.

An authorized user for the REGISTRATION OVERRIDE clause is one whose description in the dictionary 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-name
  AUTHORITY IS ALL.