Hello,
Any reason why we are not able to see non-default library in SAS EG>SASApp>Library?
How is it defined? In autoexec code, or in metadata?
If metadata, look at the permissions of the library object, and check if the user in question may read it.
Also look at the permissions of the directory in the filesystem. If the user misses rx permissions there, you will also have a problem.
thanks @Kurt_Bremser
How we can check whether its defined in autoexec or metadata?
Is there any way to check which autoexec using in SAS EG by default?
Check your metadata-defined data libraries in SAS Management Console. If the library is not defined there then it most likely will be defined in a SAS autoexec.
The autoexec used by EG is usually the one associated with your SAS application server context, usually called SASApp. Check in <SAS Home>/lev1/sasapp.
We have not defined any libraries in SMC and and autoexec default location <SAS Home>/lev1/sasapp.
Still I can see the library populated in dev env EG Is there any other autoexec calling or redirecting ?
In SAS EG in the Servers list, right click and open Properties. In the Software tab click on the View Initialization Log. This will include evidence of any autoexec run.
@japsas100 wrote:
Still I can see the library populated in dev env EG
So you have an environment where the libraries work, and another where they don't?
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.