04-03-2018 04:15 AM
SAS already offers a number of ways to do batch submission and scheduling these jobs as well. This link explains some of the options:
In addition recent versions of SAS Studio provide batch job submission as well.
My favourite way is using SAS Management Console as all the scheduling and batch functionality is server-based so it is very resilient and reliable.
Perhaps you could explain why you prefer EG to be your batch interface?
04-03-2018 11:45 AM
SAS Studio wasn't around when we first had this need, but we do intend to introduce this after we upgrade to the latest version and due to security, Base SAS is not an option. Users do utilize the EG options in that post, but that's not true batch (logoff + background) and doesn't eliminate issues outside of SAS servers (networking, desktop, etc). It's also not feasible to have admins manage schedules for our large user base, especially when jobs aren't always repeated as-is.
We have a true batch option in place, leveraging XCMD and LSF (Grid), but it would be nice if EG had it built-in like Base SAS and Studio do.
04-03-2018 05:22 AM
and we don't like to give that access out to all users.
Why? A properly administered server with a properly set up backup can never be in danger.
I can cause enough grief from SAS without using xcmd if the server is run by a donkey.
04-03-2018 11:40 AM
We have security in place, but that doesn't mean limiting XCMD isn't helpful. We're not concerned with malicious uses by advanced users, but accidental things.
04-03-2018 11:30 AM
We do have plans to add a background submission feature to EG in a future release, very similar to the one in SAS Studio. We do not know exactly when it will make it in though.