If you ever try to create a dataset or any other write function to a Metadata based Libname, from within SAS Enterprise Guide you will have encountered the old “METAOUT=DATA” error message.
What this says is that due to the libname bing a metadata based libname you can’t write to it.
Well there is an easy way to fix this:
- In SAS Management console go to the properties of the desired libname
- Click on the extended attributes tab
- Create an new entry with the following values
- Name = AssignMode
- Value = 2
- Try it via EG now and Helens your auntie (but not your prime minister – apologies to non kiwis its a GIS joke!)
This lovely option is easily found here:
http://support.sas.com/kb/20/760.html
Other option values you can use are:
0 Assign using SAS Enterprise Guide
1 Assign using the META engine, METAOUT=ALL (default META engine behavior)
2 Assign using the META engine, METAOUT=DATA
3 Assigned by the SAS server (pre-assigned)
This info (and a raft of other cool Enterprise Guide stuff) can be found here:
http://support.sas.com/techsup/technote/ts788.pdf
Hi,
I am having difficulty to control library permission esp. for EG users if the library is already assigned in autoexec file. Have you ever encounter this? If yes, please share.
The issue is likely to be that the libnames assigned in the autoexec are not being controlled by metadata and therefore may not comply with security.
I always recommend that you don’t assign any libnames via the autoexec, although we all do it in a pickle as it always works and it often takes a bit of debugin to figure out why the metadata libname doesnt work the way we want.
I have just experienced this with the LSF scheduler and metadata libnames.
Just a quick note of gratitude from Canada: Your blog was the only reference I found in Google that addressed this question directly. Thank you!
Hey Malcolm
Good to hear it helped.
Anything that lets you have more time watching Ice Hockey is a good thing
Cheers
Shane