You're talking about a local install of SAS desktop? Yes. Your laptop is a similar spec to what we were using in my organisation till about 2 1/2 years ago, when we moved to server-hosted SAS.   There's a bunch of factors involved in just how good the install-experience will be, and how well SAS will run. Best to install from a Software Depot on a memory-stick, unless you have a really fast network. It also helps if you have all the prerequisites installed prior to running the Deployment Wizard. That saves reboots, and - if the install is going to fail - it's probably something to do with a prerequisite. The Wizard is meant to take care of that, but we've had isolated instances where it didn't.   Hopefully you have an SSD in the laptop. That makes the biggest difference when running SAS locally, especially if you have data and WORK libraries on the SSD. 8GB will be enough RAM, especially if you're running 32-bit Windows 7. If 64-bit, then you may at times benefit from more RAM. Depends what else you're running. And if Windows 7 is x64, it's nicer if Microsoft Office is also x64. ... View more

Hah. Sounds like you're making progress. That's the way we assign frequently-used libraries in EG (sometimes by using a %INCLUDE) or otherwise by running the assignment code at the start of the process flow.   But you're writing to the WORK library on SASApp? If you write it to a permanent location, it won't go away. ... View more

Hi again. Thanks for that. I confess that I'm still confused. Hopefully someone more knowledgeable answer your questions. We've just got a non-distributed server environment running on Windows Server with no remaining desktop-SAS licenses, so I can't try running 1 flow on the PC and the other on a server. If I could, I'd be putting the outputs into a permanent folder on the network file-server (and not to my local C: drive, because the SAS server cannot see that).   I'll watch the thread with interest.   Cheers, Lance   ... View more

In addition to your declaring the permanent LIBNAME, have you added it to the output tablenames? e.g. data SAS_Temp.tblCITLoanList; infile datalines delimiter=","; informat Client $3.  Also, can you please clarify what you mean by the "local server"? Do you have SAS installed on your PC, with the EG Connections dialog showing "do not use a profile" as Active? I didn't think you could do parallel execution without multiple workspace server sessions. If you're using grid servers, does LIBNAME SAS_Temp 'c:\datasets';  actually succeed?   If the log shows that you've successfully written the output from the DATA steps into a permanent folder on disk (C:\Datasets), then they should still be there after you've closed EG. ... View more

Hello Poornima. There has been at least one release that I could not simply update on Mac or Windows. I've also encountered the message about the share being missing, but I was still able to access it from SAS Studio. My suggestion is that you do what I did -  delete your current virtual machine, download the full SAS University Edition again, and follow the instructions to set it up. ... View more

Wow. Proof that I should stick with my gut instincts and not believe what Sales and the Partners have been telling us 😉  Sigh. Fortunately, I insisted that we support both SAS Studio and EG, but have been recommending the use of SAS Studio where (a) the team doesn't have existing EG projects; or (b) the majority of the team has no great desire to use EG. The main concerns have been that we'd love to move to a zero-client install, and that EG wouldn't connect with Viya.   From the slides, I take it that EG will be fully compatible with Viya. So ... I guess we'll want to keep rolling out EG! Unless IT insists otherwise. Of around 100 users, about 40% continue to use EG. A fair number of those using SAS Studio wish it'd was more like EG, without the bits they don't like about EG. I'm not placing any bets on what options there'll be in 5 years time 🙂 ... View more

Final comment - we installed SAS/GRAPH NV Workshop on the desktops, but it is indeed looking for a local SAS/GRAPH license. The server is licensed for SAS/GRAPH. Next time we deploy the client-side software, we'll remove NV Workshop. We had a couple of other license issues in our move from desktop SAS to server, but - due to cost - chose to only address one. ... View more

Hello Juan,   Thanks for replying. Yes, I reviewed that thread prior to posting. The value of 'webdms.maxSessionTimeoutInHours' is set to the default of 240 on our site, which doesn't tally with the default timeout of 1 hour in SAS Studio. When change the Session time-out value in SAS Studio Preferences > Start Up, anything over 240 gives "This value is out of range". So I'm pretty confident the setting name is accurate.   As we onboard new server users we are now telling them to change the setting in SAS Studio, but not everyone reads our advice! It's turned out to be the biggest new-user annoyance. They like Batch Submit, but also want to go to lunch and leave an interactive session running. I've not yet suggested shorter lunch breaks    Lance ... View more

Thanks for that. I'm thinking that it will install okay, but not work if it needs local SAS/GRAPH functionality. There is no setting in the application to point it to a server, and I can't find a configuration file.   Will post the answer when I have it confirmed. ... View more

Yes. Same "additional product" licenses as we have on the desktop. ... View more