submitting SAS code as a batch job in EG?

[AlanC]

Let me share some info to help you understand the limitations. As a consultant, I have seen SAS installations from 1 person to over 2500 EG users. Recently, I was at a site with over 500 SAS/EG  users and 1 or 2 admins. They also had constrained computing platforms. Hence, the admins had no idea what was happening in the dozens of depts across the company.

If an EG user could just schedule jobs, the system would become quickly overloaded. If that person left, the job would continue indefinitely because it would be scheduled at the server. 

As I have mentioned to people before, you don't have to be constrained by any UI application's functionality. Use an RPA tool such as AutoHotKey and just do your manual tasks using a simulated user.

[AhmedAl_Attar]

@kschott,
Quick ways to figure out What's your SAS Server (Windows/Linux) , Submit the following in a Program Entry
1. %put _all_; *<-- Prints your SAS server automatic macro variables;
2. %put %sysfunc (pathname(WORK)); *<-- Prints the WORK library physical folder location

Look through these outputs and you should be able to figure out the nature of your SAS server.