Validating a Metadata-Bound Library :: SAS(R) 9.4 Guide to Metadata-Bound Libraries, Second Edition

Overview

Validating a metadata-bound library identifies any inconsistencies between the physical metadata-bound library and its corresponding metadata objects. The validation report lists any missing or mismatched physical tables, security location information, and metadata objects for a specified physical library.

To validate a metadata-bound library, use either SAS Management Console or the AUTHLIB procedure.

Tip

In general, you perform this validation against a physical library that is already bound to metadata. However, you can also perform this validation against a traditional library, in order to determine whether any individual physical tables within that library are bound to metadata.

Requirements

In order to validate a metadata-bound library, the following requirements must be met:

The workspace server (or SAS session) that makes the request must run under an account that has host-layer Read access to the target physical library. This is necessary in order to assign the libref.
The workspace server (or SAS session) that makes the request must connect to the metadata server as an identity that has the ReadMetadata permission for the target secured library object and secured table objects.

GUI Method

Introduction

To generate a metadata-bound library report in SAS Management Console, select the Report action on a secured library object. The report identifies any missing or mismatched security information for the corresponding metadata-bound library and its tables.

Note: In SAS Management Console, the report action is available for only secured library objects. To use SAS Management Console to generate a report for a traditional (unbound) library, initiate the task from any secured library object and enter the path of the target physical library in the Secured Library Report window.

Instructions

On the Folders tab in SAS Management Console, beneath a /System/Secured Libraries branch, locate the secured library object that corresponds to the metadata-bound library that you want to validate.
Right-click the object and select Report.

The Secured Library Report dialog box appears:

Refer to the entries in the preceding example as you complete steps 3 through 5.
Select the application server that you want to use to generate the report.

Note: The application server must include a standard workspace server that has host access to the target directory.
Specify the directory path of the target metadata-bound library.
If the library includes one or more AES-encrypted tables and the key is not recorded in the library’s metadata, select the Encrypt Key check box and enter the key to open the data sets.

Note: The key that you enter is placed in quotation marks when it is submitted to SAS and is therefore case sensitive. If the key was originally specified in SAS code without quotation marks, then be sure to use uppercase letters when entering it here.

Note: If the library contains a table that is encrypted with a different key, the message Invalid ENCRYPTKEY will appear in the report output.

If a key is recorded in the library’s metadata, you can leave the Encrypt Key field blank. The stored key will be used to open the data sets.
Click OK.
In the Secured Library Report window, click Yes to view the report and the log.

Code Method

As an alternative to using SAS Management Console, you can use the AUTHLIB procedure to generate a metadata-bound library report. See REPORT Statement.

Results

It is important to carefully examine the entire report. The first section of the report lists all physical tables that are properly bound. Subsequent sections list any physical tables that are not properly bound and identify any other discrepancies.

Tip

To generate the report in HTML format, use the AUTHLIB procedure (instead of SAS Management Console). For an example, see REPORT Statement Results for the ABCDE Library.