Everyone thanks for the input. From the feedback I conclude that I need to further clarify my question. Some wrong assumptions/conclusions were drawn that I would like to get out of the way. - The number and kind of servers underneath a Lev server depends on the server topology and SAS license. We have a metadata server on it's own separate machine, so that one is out of the equation. For us one Lev can contain ObjectSpawner, ConnectSpawner, ShareServer, SPD Server, Dataflux Data Management Server and a an arbitrary amount of app server contexts (SASApp, SASWeb, SASETL; SASMeta is absent here). These server each have their own set of usermod config files. - DTAP tiers are not combined in a single metadata repository, let alone server. We "segregate those by segregation in levels". For us a Lev is the home of a single tier in the DTAP setup. We strive for separation at the machine level but that is not always the most economical or practical approach, hence multiple Lev's on a single machine. I had hoped that would be clear from my explanation. But eg Lev1 is Dev and Lev2 is Test. Or whatever. Lev1 and Lev2 would never share the same metadata server. That's how SAS designed it. So how are we mixing up DTAP tiers at the metadata level? I agree with Jaap that would be a very bad idea. Exactly why we are not doing it. So say Lev1 is Dev and I want Dev to have its own SASWORK location, different from Test aka Lev2 (or, as in my example in the original post, SASUSER). I would like to define that in a config at the Lev level and not multiple times underneath that for every server component that is housed there. Call me lazy. ... View more

Hi Lavi and all, This question was never answered. There is a similar thread () that also was not answered, at least to my satisfaction. I would like to get some attention to this again as I am struggling with the same. The quote in the original post holds, but only for a single group. So if you have Lara in authdomain OracleProdAuth and authdomain OracleDevAuth than both logins can be defined for group A but not one in group A and the other in group B. I would argue both logins are not the same in both cases and it should be allowed. My thought: just because the accounts sound the same doesn't mean they are. So I hope someone can shed some light on these matters, either regarding the ratio behind this behaviour or a solid approach. ... View more

Hi Linus, Using _output_col0_exp actually shows my problem. It contains an unqualified reference to the mapped column so the originating table cannot be established. Bottom line is I think there is no straightforward solution. Anyways I am still looking for the macro code. I once downloaded it but lost the file and now the link is broken. Anyone? Regards Jan ... View more

Hi Tim, I would like to download the file but the link seems broken. I get some sort of server error. Can you help? TIA, Jan. ... View more

Hi Hardy, I am out of suggestions. If everything runs from the local server and is a fresh install (assuming SAS 9.3 and EG 5.1) then network issues are indeed unlikely. I would keep an eye on the load you're imposing on your machine. Maybe it's underpowered for the task. All I can (and must) suggest is to contact tech support again if you really think something is wrong. Good luck, - Jan ... View more

Hardy, Many times a company's network infrastructure has components (mainly routers, firewalls) that discard network connections after a set idle time. I have seen this affecting EG much the same way as you describe. Both connections to metadata and workspace servers can be forcefully terminated by this and render EG unresponsive. Maybe you can talk to your network folks to work this out. It worked for us. I hope this can help resolving your issue. - Jan ... View more

Hi, DI 3.4 may not support my approach; I haven't checked. What I do in 4.x, in a nutshell, is to 1) define the CSV in the metadata with a macro variable reference as the filename  (like &csvfile). make certain the generated code wraps this in double quotes or you're stuffed. This may actually be the breaking point for 3.4. 2) define and load a table that holds files present in your input location and keeps track of their processed status, eg through a timestamp. 3) Then in a job process that table in the first step to find out which file must be processed. Stick that value in a macro var. As the next step process the external file you defined in the metadata. Give that step a parameter to transfer the result from step 1 into the macro variable that matches the filename of the CSV file from 1). As a last step (or a subsequent job) mark the file as processed in the table as defined in 2). Good luck, Jan. ... View more

I have worked with quite a few organizations that implement all sort of desktop virtualization products. The gains in terms of systems maintenance and admin are huge as they usually have large numbers of users. Local installs over network or by walking around with a dvd or usb stick are behind us. Also it becomes more and more "not done" to provide people with the local admin rights on workstations to install things. Depending on your other duties I think that even with 4 people you can save a lot of headaches and money by using such an approach. Just think of SAS hotfixes and upgrades, new users, hardware failures and upgrades. I think I don't need to spell it out. Do mind the official SAS statement on virtualization at http://support.sas.com/techsup/pcn/virtualization.html. Support is limited to certain providers and technologies. They just don't have the time or means to test all their software on the growing number of possible permutations of products on the market. If it's not supported doesn't mean it won't work. But your mileage may vary. SAS may ask you to replicate a problem on bare metal if you have a problem. And you have a burden to test it thoroughly during deployment. But if it does work the benefits are plenty and your boss will love you for it. - Jan ... View more

Can you give us some more detail on the libraries? Eg what type are they (SAS, dbms, ..)? Be aware that the METAAUTOINIT option is now default for 9.2 and 9.3. This option impacts the way libraries are assigned when a SAS server starts up. So check what you had in 9.1.3. I wish you all the best in your new role as SAS admin. Regards Jan. ... View more

Thanks Chris this wonderful news. I do use 4.3 at other sites but had not noticed this. I think, from a sys admin point of view, this is a change for the better. By the way the case at hand is at the Dutch site you payed a visit last week. While still stuck at 4.1 I figured out why the suggestions in note 10788 do not work. The pathname for work changes after the workspace server autoexec completes. I have some code in the ws autoexec that does LIBNAME EGTASK (WORK);.If I output the pathnames in the autoexec  I get: work  : /usr/tmp/SAS_workF43C000060AF_atom egtask:   /usr/tmp/SAS_workF43C000060AF_atom But in EG things have changed: work  : /usr/tmp/SAS_workF43C000060AF_atom/SAS_workBD43000060AF_atom egtask: /usr/tmp/SAS_workF43C000060AF_atom So the intended redirection of EGTASK to WORK does not work. I see this only happening when done from a code node in EG itself which we do not want to burden out users with. So final conclusion is: we live with it until 4.3 is implemented. BTW: Nice trickery to re-assign work after SAS has started. Didn't think this was possible. ... View more

Hi Michelle, thanks. I am aware of this. In fact what we trying to achieve is to avoid users to have to go through these steps. They forget or ignore this. regards Jan. ... View more