AUTHLIB Procedure

TABLES Statement

Used after a CREATE, MODIFY, REPAIR, and REPORT statement to specify the tables to process a statement action and to specify the current passwords on the data sets, if different from the metadata-bound library passwords.
Default: When no TABLES statement is specified, the TABLES _ALL_ statement is the default behavior.
  • The TABLES statement can follow only a CREATE, MODIFY, REPAIR, or REPORT statement.
  • A connection to the target metadata server.


Optional Arguments

is required if any options are included, such as passwords or MEMTYPE=. Here is an example:
tables table-name / pw=password;
specifies the current password of the data set.
specifies the current ALTER= password of the data set.
specifies the current READ= password of the data set.
specifies the current WRITE= password of the data set.
restricts processing to a single member type of DATA or VIEW. If not specified, the default is both types.
specifies SAS data file member type.
specifies SAS view member type.
Alias:MTYPE=, MT=
the external identity of the secured table object that was assigned when the object was created and that is stored as part of the location information in physical data sets that are bound to the secured table object.
Restriction:SECUREDTABLEGUID= option is used only in TABLES statements that follow certain REPAIR statements.


Using the TABLES Statement

If you lose the password (or passwords) for a metadata-bound library, you cannot unbind the library or change its passwords.
Be sure to keep track of passwords that you assign in the CREATE and MODIFY statements.
The TABLES statement is primarily used to specify the current password(s) on data sets when different from the current metadata-bound library required password(s). It usually follows a CREATE or MODIFY statement to make the data set passwords change to the metadata-bound library passwords. See Securing a Library When Existing Data Sets Are Protected with Different Passwords.
If you are removing the binding of the physical library to metadata or the physical library is not bound to a secured library, then you might want to modify the data set passwords to some other value. You are not restricted to changing to a common metadata-bound library password. In that case, you might choose to specify both a current and new password separated by a slash / for data sets in a TABLES statement.
TABLES _NONE_ can be used to limit the action of the previous CREATE, MODIFY, or REPAIR statements to the library level and not apply the action to any table. TABLES _ALL_ is the default behavior if no TABLES statement is specified. You might wish to write an explicit TABLES _ALL_ if you want to specify password options to apply to all data sets.

Using the TABLES Statement with the CREATE Statement

The CREATE statement can be followed by one or more TABLES statements to specify current passwords for data sets when different from the metadata-bound library passwords. If the TABLES statement is not used, only two groups of data sets will be bound:
  • data sets without passwords
  • data sets with passwords matching the metadata-bound library
In effect, omitting TABLES statements is equivalent to specifying one TABLES _ALL_ statement. For more information, see CREATE Statement.

Using the TABLES Statement with the MODIFY Statement

The MODIFY statement can be followed by one or more TABLES statements to specify modifications to passwords in the data sets. If no TABLES statement follows the MODIFY statement, there is an implicit TABLES _ALL_ statement. A separate TABLES statement is required for sets of data sets (tables) that might have different current passwords. For more information, see MODIFY Statement.

Using the TABLES Statement with the REPAIR Statement

When using the REPAIR statement, one of the ADD, UPDATE, or DELETE actions must be specified. LOCATION, METADATA, or both are used to clarify if the action is to apply to the physical security information in file system, to the metadata objects in the SAS Metadata Server, or to both. The REPAIR statement can be followed by one or more TABLES statements to perform the same action on the specified data sets. For more information, see (Preproduction) REPAIR Statement.

Using the TABLES Statement with the REMOVE Statement

Using a TABLES statement with a REMOVE statement that does not select all tables will produce an ERROR and not execute.

Using the TABLES Statement with the REPORT Statement

The TABLES statement is syntactically accepted with the REPORT statement but has little or no use.