Hi Tammy,   That error message indicates it couldn't find the required library object. This could be due to a typo in the parameters or that the metadata identity being used doesn't have appropriate permissions to see the required library.    In your example, is edwref the library name (i.e. the name of the metadata object that can have spaces in it) or the libref (standard libref naming rules - max 8 chars etc). Judging by the shortness of it I am wondering if it is the libref?   The library option is used to specify the name of the library and may appear to work if the library name is the same as the libref. If you want to look up a library by its libref then you need to switch to the liburi option and specify a query string that will uniquely identify the library. There are some examples in the documentation page LIBNAME Statement for the Metadata Engine. If edwref is a libref you can try:   libname tamedw2 meta liburi="SASLibrary?@libref='edwref'"; Bear in mind that if you have 2 libraries registered with the same libref then you'd need to add additional query string qualifiers to ensure you only get 1 result (or have unique names and switch back to using library= with the object name).   Cheers Paul ... View more

Hi Tammy,   The easiest way is to pre-assign them (in metadata or server autoexec). You can still pre-assign them using the Metadata Libname Engine (MLE) if you want to take advantage of metadata security. You'll want to be aware of all the intricacies regarding what you can and can't do with MLE libraries for the various metaout options. One of my favourite papers on this topic is What SAS Administrators Should Know about Libraries, Metadata, and SAS Enterprise Guide (SAS 9.2, SAS Enterprise Guide 4.2 & 4.3). It was written for SAS 9.2 but much of it is still relevant with SAS 9.4.   You could also get your users to use MLE in their libname statements (so the physical location is maintained in metadata) and possibly use EG autoexecs too.   If you need to protect the tables with metadata security even if the users bypass metadata and write their own libname statements you could also consider using SAS Metadata-Bound Libraries.   If you do pre-assign, just be aware that it may impact other apps too and if there are any database-backed libraries it may add additionally latency into any existing processes. There are a few different ways or handling this: defer=yes, dedicated custom app servers etc.   Cheers Paul ... View more

If you haven't seen it, there's a really good checklist by David Stern: Checklist of SAS Platform Administration Tasks ... View more

Hi Ronan,   Glad to hear the link to that SAS note helped you too. I was initially puzzled when I ran it and got no output. I was expecting it to print usage info to the console like the other SAS Platform Object Framework utilities do. It wasn't until I was looking around for a log file with errors that I saw the usage info and then that note confirmed it.   I was finding that I had to specify most of the parameters to get it to work and it would just log "null" and return 1 when I didn't get the complete set required. It would probably be easier to just point it at a profile (.swa) but here is an example that worked for me:   # Validate Logical Workspace Server /opt/sas94/sashome/SASPlatformObjectFramework/9.4/ValidateServer -msp "host=localhost port=8561 domain=DefaultAuth userid=myuserid password={sas002}MYPWENCODEDPASS reposid=A0000001.A9ZZZZZ9" -sn "SASApp - Logical Workspace Server" -cred "domain=DefaultAuth userid=myuserid password={sas002}MYPWENCODEDPASS"; echo $?   Examples for servername (sn) that worked for me were: SASMeta - Logical Metadata Server SASMeta - Metadata Server SASApp - Logical Workspace Server SASApp - Workspace Server SASApp - Logical Pooled Workspace Server SASApp - Pooled Workspace Server SASApp - Logical Stored Process Server SASApp - Stored Process Server SASApp - Logical OLAP Server SASApp - OLAP Server SASApp - Connect Server SAS Content Server Operating System Services - hostname I have found that a typo in the server name logs "null" and returns 0.   I didn't want to duplicate the credentials (assuming credential caching would be used) but if I didn't then it logged  "A null user ID is invalid for creating a User Context." and returned 1. When it works it returns 0. Cheers Paul ... View more