Restrictions: |
Users cannot access metadata-bound data sets from any
release of SAS prior to the second maintenance release of SAS 9.3.
|
The AUTHLIB procedure is intended for use by SAS administrators.
Users who lack sufficient privileges in either the metadata layer
or the host layer cannot use this statement.
|
The AUTHLIB procedure cannot operate on libraries that
are assigned for access through a SAS/SHARE server.
|
The physical library specified cannot be a concatenated
library, temporary library, or accessed through a SAS/SHARE server
and must be processed by an engine that supports metadata-bound libraries.
|
Requirement: |
The AUTHLIB procedure requires a connection to the target
metadata server.
|
Tip: |
Each password and encryption key option must be coded
on a separate line to ensure that they are properly blotted in the
log.
|
See: |
SAS Guide to Metadata-Bound Libraries |
Statement |
Task |
Example |
PROC AUTHLIB |
Create and manage metadata-bound libraries |
|
CREATE |
Create the secured library object in the SAS Metadata
Server and record the physical security information in the directory
or bound files
|
Ex. 1, Ex. 2, Ex. 3, Ex. 4, Ex. 11, Ex. 10, Ex. 12, Ex. 13, Ex. 15 |
MODIFY |
Modify password values and encryption key values for
a metadata-bound library
|
Ex. 5, Ex. 6, Ex. 16 |
PURGE |
Removes any retained metadata-bound library credentials
older than a given date of replacement.
|
|
REMOVE |
Remove the physical security information and metadata
objects that protect a metadata-bound library
|
Ex. 7 |
REPAIR |
Recover security information (in physical data) or
secured library and table objects (in metadata)
|
|
REPORT |
For a specified metadata-bound library, compare physical
library contents with corresponding metadata objects (in order to
identify any inconsistencies)
|
Ex. 8 |
TABLES |
Specify which tables within a specified metadata-bound
library are affected by certain AUTHLIB statements
|
Ex. 4, Ex. 9, Ex. 11, Ex. 10, Ex. 12, Ex. 15, Ex. 16 |