Beginning with the first maintenance release for SAS^® 9.3 (TS1M2), you can bind Base^® SAS libraries to SecuredLibrary objects in a SAS^® Metadata Repository. To determine whether a library is bound to a SecuredLibrary object, the Base SAS LIBNAME engine must look within the library for a subfolder named .sassl. The presence of the .sassl directory indicates that the library is bound to metadata.

Read permission only enables you to read the directory and see the contents. You cannot open or perform any other operation on the files or subfolders contained within that library. Therefore, Execute permission is required in order to see whether the .sassl subdirectory exists and what information it contains.

Failure to grant the appropriate Read and Execute permissions to a Base SAS library prevents the library from being assigned successfully. In the case of reserved system libraries, such as SASUSER, failure to assign the library can result in a failure to initialize SAS. When that happens, error messages similar to the following are generated:

ERROR: Encountered error when the V9 engine tried to determine if SASUSER has a registered secured library object location.
ERROR: User does not have appropriate authorization level for /sas/sas93/myuser/sasuser/.sassl.
NOTE: Unable to initialize the options subsystem.

To correct the errors and enable the SAS session to open properly, be sure to grant Read and Execute permissions to the SASUSER library in the host operating system.

Operating System and Release Information

A fix for this issue for Base SAS 9.3_M2 is available at: