Required Argument

library-identifier

specifies a SASLibrary object, which defines a SAS library. This SAS library contains the tables whose metadata is updated. The SASLibrary object can be specified using any of the following forms:

LIBID=<">identifier<">

specifies the 8-character metadata identifier of the SASLibrary object that represents the library. The 8-character metadata identifier is the second half of the 17-character identifier. For more information, see Metadata Object Identifiers and URIs.

LIBRARY=<">name<">

specifies the value in the SASLibrary object's Name= attribute.

LIBURI="URI-format"

specifies a URI, which is a standard from SAS Open Metadata Architecture. For more information, see Metadata Object Identifiers and URIs. The following URI formats are supported:

LIBURI="identifier.identifier"

specifies the full 17-character metadata identifier, which references both the repository and the object. This syntax is equivalent to specifying both LIBID= and REPID=. An example is liburi="A58LN5R2.A9000001".

LIBURI="SASLibrary/identifier.identifier"

specifies the SASLibrary object type, followed by the full 17-character metadata identifier. This syntax is equivalent to specifying both LIBID= and REPID=. An example is liburi="SASLibrary/A58LN5R2.A9000001".

LIBURI="SASLibrary?@attribute='value'"

specifies the SASLibrary object type, followed by a search string. Examples are liburi="SASLibrary?@libref='mylib'" and liburi="SASLibrary?@engine='base'".

Requirements:You must enclose the LIBURI= value in quotation marks.

The URI must resolve to a single metadata object. When using an attribute qualifier like @engine=’base’, if you have more than one Base library defined in metadata, PROC METALIB returns WARNING: Multiple metadata objects found.

Note:SAS Data Integration Studio can process work tables that exist temporarily in the Work library. The metadata type is WorkTable. Usually, work tables are not assigned to a library and have no library metadata, but they do have table and column metadata. A work table that results from a generated transformation can be dynamic in nature. In other words, its structure might be modified by the transformation. PROC METALIB can update the metadata to match the work table. If there is no library assignment, submit a blank library specification, and identify the work table with the SELECT statement. Here is an example with a blank library specification: proc metalib; omr (libid="" repid="A5O7HLNB"); select ("A5O7HLNB.A9000001"); run;

Tip:In SAS Management Console, avoid the Pre-assigned Library template. When you pre-assign a library, choose the resource template that is specific to the type of data source library that you are creating, and select the This library is pre-assigned check box. The Pre-assigned Library template is intended for certain system libraries only, and it does not work for other libraries. In addition, for PROC METALIB, you must submit the library pre-assignment in the current SAS session. You can store the LIBNAME statement in an autoexec file, or you can submit the LIBNAME statement in your SAS session before you submit the procedure.