I was planning to automate running SAS EGP to run in batch.
Scheduler calls a power shell script that would run the EG project. The EG log will not be written to any file and the error code would be caught.
The following link gives the error code that SAS program would return when running on batch mode on windows.
Are these codes the same if we run the SAS enterprise guide project in windows in batch mode using power shell script (not VB script).
@Sajid01 Correct. Those codes are returned regardless of the way you run the SAS program in batch.
BTW, PC-based scheduling has other issues. For example network glitches, software updates, someone else being logged on, someone turning it off...the list goes on. Server-based scheduling is inherently more reliable (I'm assuming you have remote SAS servers here) if that is important to you. The downside is having to export your code from EGPs first.
@Sajid01 Correct. Those codes are returned regardless of the way you run the SAS program in batch.
BTW, PC-based scheduling has other issues. For example network glitches, software updates, someone else being logged on, someone turning it off...the list goes on. Server-based scheduling is inherently more reliable (I'm assuming you have remote SAS servers here) if that is important to you. The downside is having to export your code from EGPs first.
Good news: We've extended SAS Hackathon registration until Sept. 12, so you still have time to be part of our biggest event yet – our five-year anniversary!
Check out this tutorial series to learn how to build your own steps in SAS Studio.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.