Step 2: Associating a User and WHERE Criteria with the Security Name

Restricting Access to Rows › Assigning Row-level Security to Data Tables › Assigning Row-level Security › Step 2: Associating a User and WHERE Criteria with the Security Name

Step 2: Associating a User and WHERE Criteria with the Security Name

To restrict access to the table by Forrest and prevent him from viewing salary information exceeding $50,000, Fran Snell wants to specify WHERE criteria. If no criteria are specified, Forrest will be able to view the entire APPLICANT table including all the salaries.

To enter WHERE criteria for the table, perform the following steps:

Type RLOD in the screen name field of any screen and press [Enter] to access the Load Data option for the SRT:

                                              CA
 PF1 = ADD;PF2 = CHANGE;PF3 = DELETE;PF4 = VALIDATE;ENTER = NEXT;CLEAR = EXIT
  $SECURITY-RUNTIME-TABLE$

  GROUP

  USER

  OWNER

  SECURITY-NAME

  STATUS

  WHERE-CLAUSE

Specify the following information on the RLOD screen:

USER—The user ID of Forrest (FORREST) so he can access the table.
OWNER—Snell's user ID (SNELL).
SECURITY-NAME—The security name of the table to which you are applying row-level security (SALSEC).

WHERE-CLAUSE—The restrictions that define the data Forrest will be allowed to see (COL(SALARY REQUIREMENT) LT 50000).

CA PF1 = ADD;PF2 = CHANGE;PF3 = DELETE;PF4 = VALIDATE;ENTER = NEXT;CLEAR = EXIT $SECURITY-RUNTIME-TABLE$ GROUP USER forrest OWNER snell SECURITY-NAME salsec STATUS WHERE-CLAUSE col(salary requirement) lt 50000

Press [PF1] to add the row.
Press [PF4] to validate the entry:

CA NO ERRORS ON VALIDATION $SECURITY-RUNTIME-TABLE$ GROUP USER OWNER SECURITY-NAME STATUS WHERE-CLAUSE