Previous Topic: Securing the DictionaryNext Topic: AUTHORITY Clause


PREPARED/REVISED BY Clause

The PREPARED/REVISED BY clause supplies a user ID and optionally, a password. The DDDL compiler uses this information to determine whether the requested user is authorized to perform secured operations or access a secured entity type or entity occurrence.

The PREPARED/REVISED BY clause within an individual entity-type statement overrides, for that statement only, the default PREPARED/REVISED BY specification, if present. The default PREPARED/REVISED BY specification is determined by the user ID supplied by one of the following, in order of precedence:

  1. PREPARED/REVISED BY clause in the SET OPTIONS statement
  2. DDDL compiler signon procedure
  3. System signon procedure

A PREPARED/REVISED BY clause can appear in any ADD, MODIFY, REPLACE, DELETE, and DISPLAY/PUNCH statement associated with any entity type. PREPARED BY can be used when a new comment key definition is added to the dictionary; REVISED BY can be used when a comment key is changed.

The DDDL compiler reads in the entity-occurrence identification, then performs a security check. The compiler checks the user specified in the default PREPARED/REVISED BY clause and in any additional PREPARED/REVISED BY clauses. If neither of the requested users is authorized, the DDDL compiler rejects the entire statement. If at least one user is authorized, the DDDL compiler processes the statement.

Syntax: PREPARED/REVISED BY Clause

►►─┬─ PREpared ─┬─ by user-id ─┬─────────────────────────┬────────────────────►◄
   └─ REVised ──┘              └─ PASsword is password ──┘

Parameters

PREpared by

Supplies a PREPARED BY specification for the named entity occurrence.

REVised by

Supplies a REVISED BY specification for the named entity occurrence.

user-id

Identifies the user requesting the ADD, MODIFY, REPLACE, DELETE, DISPLAY, or PUNCH operation. User-id must be a 1- through 32-character value and must be enclosed in quotation marks if it contains embedded blanks or delimiters. The specified ID must correspond to the ID of a user in the dictionary. If the requested entity occurrence is secured, the named user must be authorized to perform the requested operation. The DDDL compiler adds the authority of the user specified in the PREPARED/REVISED BY clause to the authority of the signed-on user to validate user-entity authority.

PASsword is password

Specifies the password associated with the named user. Password must be a valid 1- through 8-character password and must be enclosed in quotation marks if it contains embedded blanks or delimiters. If the named user has not been assigned a password, this parameter is invalid. DDDL suppresses the password when it echoes the command.

Example

In the following statement, user DGS adds the system named ACCOUNTING to the dictionary; DGS becomes the PREPARED BY specification for ACCOUNTING, overriding the default PREPARED BY specification established at signon or in a SET OPTIONS statement.

add system name is accounting
     prepared by user dgs.

Usage

Using PREPARED/REVISED BY for security

When you use this clause for security purposes, the PREPARED/REVISED BY clause must immediately follow the entity-occurrence identification.

SET OPTIONS may impact PREPARED/REVISED BY

If the USER SIGNON OVERRIDE clause of SET OPTIONS is set to OFF (or NOT ALLOWED), the PREPARED/REVISED BY clause is ignored and a warning message is displayed.