Validating a Metadata-Bound Library :: SAS(R) 9.3 Guide to Metadata-Bound Libraries

About Validating a Metadata-Bound Library

For a specified physical library, the REPORT statement of the AUTHLIB procedure lists any missing or mismatched physical tables, security location information, and metadata objects.

Tip

In general, you use the REPORT statement against a metadata-bound library. However, you can also use this statement against a traditional library in order to determine whether any individual physical tables within that library are bound to metadata.

Who Uses the REPORT Statement?

Administrators use the REPORT statement of the AUTHLIB procedure to identify any inconsistencies between a physical metadata-bound library and its corresponding metadata objects.

In order to use the REPORT statement, you must meet the following criteria:

Your SAS session runs under an account that has host-layer Read access to the target physical library. This is necessary in order to assign the libref.
Your SAS session connects to the metadata server as an identity that has the ReadMetadata permission for the target secured library object and secured table objects.

Example

In this example, you use the REPORT statement to determine whether there are any inconsistencies between a metadata-bound library and its corresponding metadata objects.

libname secdemo 'path';

proc authlib library=secdemo;
   report;
run;

Note: The preceding code does not explicitly supply connection information for the metadata server. This example assumes that your SAS session already knows how to connect to the target metadata server.

In this example, no inconsistencies exist. The following image depicts output from the preceding code.

Validating a Metadata-Bound Library

About Validating a Metadata-Bound Library

Who Uses the REPORT Statement?

Example

See Also