Hello,
My name is George and I am SAS Technical Support Engineer.
Here is a quick explanation of how SAS Enterprise Guide submits code to a SAS server to be executed.
SAS EG in itself is just a visual client interface that allows you to submit code to a SAS server, but without either a Local connection to SAS or a remote SAS server connection, no processing can occur.
When you are connected to a SAS server via SAS EG, you have established what is called a Workspace Session, which is ultimately tied to an actual running SAS executable. This executable is launched via the Workspaceserver.bat file, which is simply a batch file that calls the SAS process to run with whatever options specified.
Once the code is run and results are generated, they are sent back to SAS EG where the end user can visually see the outcome.
When you connect to a SAS server from EG, you are basically running SAS Foundation on the server. For example, on a Windows SAS Server, you would actually see a sas.exe process tied to each user running EG (that is connected), from the Windows Task Manager.
SAS on the server is not running as a service, however, the SAS Metadata Server and the SAS Object Spawner are services being run behind the scenes.
I hope this helps.
Thanks,
George
... View more