11-21-2017 09:37 AM
Not sure this is the best sub-forum, so mods please move if you feel necessary.
We have some SAS projects that are run via Windows Scheduler. They run for a bit, but then run for a few seconds and do nothing. These jobs typically take about 30 mins. to run. But it seems that after about a week of successful runs, they initiate, say they run, and finish, all in about 9 seconds.
Has anybody heard of this happening and any resolutions? This is very weird.
Perhaps a Windows Scheduler alternative?
11-21-2017 09:54 AM
What do the logs say?
Note that one of the inherent advantages of running SAS codes (.sas files) in batch is the fact that you can easily keep the log of every run, as nothing needs to be overwritten.
11-21-2017 10:27 AM
Indeed, check the log files.
For an alternate to Windows Scheduler, take a look at SplinterWare. Outperforms WS by miles, only $30 for a license, 30 day free testing
11-21-2017 10:44 AM
Here is the rub guys.....
The, there is NO SAS log. Windows scheduler will says it starts the task, then 9 seconds later it says task completed. SAS never executes. This does not happen for all SAS projects. And some, no matter what machine we run them on, will start off running ok, then the same "9 second funniness" returns. This really is not a SAS issue, I don't think, but any insight is great.
11-21-2017 02:25 PM
Convert your projects to .sas files and run them in batch.
This gives you much more options than scheduling projects (other schedulers, other operating system).
11-22-2017 10:23 AM
I have exported the EG project to a .sas file. Oddly enough it will not run:
2 Libname UDRDWPRD ORACLE 'UDRDWPRD.world' ; ERROR: Incorrect syntax for this LIBNAME statement. This engine does not accept a physical name. ERROR: Error in the LIBNAME statement.
This was not touched by me. Just the standard File Export All Code In Project