SASCATCA Library?

[Kenny]

This SAS library showed up in my session, and is pointing to my physical WORK library location? What is this library, and why is it showing up? SASCATCA.

[alexal]

@Kenny ,

What version of SAS is that? I assume this is a connection from SAS Enterprise Guide? Do you have any ideas if this is a grid connection or not?

[Kenny]

SAS 9.4, M5. Yes, it is a Grid implementation. If it is tied to our configuration, I can get SAS tech support involved. I just want to understand. It started when I noticed that some of the WORK output tables I generate are labeled as USER.TABLE instead of WORK.TABLE, and our USER system option is currently defaulting to WORK (USER=). I thought perhaps this SASCATCA was related to the issue.

[alexal · Accepted solution]

@Kenny ,

Thanks for your response. SAS/CONNECT contains the elements of Remote Library Services (RLS), the same as SAS/SHARE. SASCATCA library is automatically assigned in order to cache catalogs for transport via RLS. There is no way to hide that library.

[Reeza]

Whenever you have a library defined as user that takes precedence over the work library. Data sets without a library definition are automatically piped to User over work when that library exists. This is noted in the documentation but unless you've seen it, don't know it happens/exists. It's a good trick to re-route things when your work library is too small.

[Kenny]

Thanks Reeza,

I saw the SAS doc on the USER library. This issue is either a Studio bug, or the infrastructure on our side. The behavior only occurs in Studio, and so far it appears random. When I am explicitly using the WORK library, and our USER option is 'USER=', with no value supplied, I do not expect to see any output referencing the USER library. According to the doc, our USER option defaults to WORK since we do not supply an alternative location. So why then would SAS Studio generate a table that does not show up when the job ends, and shows only a reference to the USER location?The table is actually in the WORK library, but I have to open that library and double-click the table to view it. 

My goal is to figure out why that is happening at all. What is making Studio think that any output table should go to USER?

P.S. I thought this might be related to the SASCATCA library, but I can see that is unlikely.