AUTHLIB Procedure

CREATE Statement

Binds a physical library to metadata by generating corresponding metadata objects in the SAS Metadata Repository and creating a record of the metadata objects in the physical directory.

Requirement:

A connection to the target metadata server. For more requirements, see Requirements to Use PROC AUTHLIB Statements.

Syntax

PROC AUTHLIB <option-1 <...option-n>>;

CREATE

SECUREDLIBRARY=’secured-library-name’
<SECUREDFOLDER=’secured-folder-path’>
<LIBRARY=libref>
PW=all-password-value | |
ALTER=alter-password-value
READ=read-password-value
WRITE=write-password-value;

Required Arguments

SECUREDLIBRARY='secured-library-name': names the secured library object in the SAS Metadata Server.

Alias:SECLIB=

Restriction:The total length of the secured library object pathname including the fully qualified secured folder path cannot exceed 256 characters.

PW=all-password-value: sets a single password for a metadata-bound library.

ALTER=alter-password-value: sets one of a maximum of three password values for a metadata-bound library.

READ=read-password-value: sets one of a maximum of three password values for a metadata-bound library.

WRITE=write-password-value: sets one of a maximum of three password values for a metadata-bound library.

Optional Arguments

SECUREDFOLDER='secured-folder-path': is the name of the metadata folder within the /System/Secured Libraries folder tree where the secured library object will be created.

If the SECUREDFOLDER= option is not specified, the metadata-bound library is created directly in the /System/Secured Libraries folder of the Foundation repository. If the SECUREDFOLDER= option does not begin with a slash (/), it is a relative path and the value will be appended to /System/Secured Libraries/ to find the folder. If the SECUREDFOLDER= option begins with a slash (/), it is an absolute path and the value must begin with /System/Secured Libraries or /<repository_name>/System/Secured Libraries.

Alias:SECFLDR=

Restriction:The total length of the secured library object pathname including the fully qualified secured folder path cannot exceed 256 characters.

LIBRARY=libref: name of the physical library for which the secured library object is created and the security information is stored.

If the LIBRARY= option is not specified, the physical library from the AUTHLIB procedure is used.

Alias:LIB=, DDNAME=, DD=

Restriction:The physical library specified cannot be a concatenated library or temporary library and must be processed by an engine that supports metadata-bound libraries.

Details

Specifying Passwords

If your physical library does not contain password-protected data sets, you need to specify the new metadata-bound library password(s) with either the PW= option or READ=,WRITE=, and ALTER= options in the CREATE statement. This is the most common case. See Binding a Physical Library That Contains Unprotected Data Sets.

If your physical library contains some password-protected data sets that all share the same current set of passwords, then you can specify the most restrictive password on the data sets before a slash (/) in the CREATE statement password option(s) and the new password(s) after the slash (/). See Securing a Library When Existing Data Sets Are Protected with the Same Passwords.

If your physical library contains password-protected data sets with different sets of passwords, then you can specify the data sets with each set of passwords on separate TABLES statements (see Securing a Library When Existing Data Sets Are Protected with Different Passwords) or you can subsequently use MODIFY and TABLES statements to change the passwords after the library has been bound with the CREATE statement (see Changing Passwords on Data Sets ).