12-05-2013 02:23 PM
We have a couple of conditions set up in our SAS Enterprise Guide project to run certain SAS jobs depending on whether it is the 1st or 5th of the month. These work correctly & as expected when the SAS projects are run manually. However when the jobs are scheduled in batch they don’t.
Anyone know off-hand of any reasons why this may not work? We were just wondering if there was something in the set-up that didn't allow these to work. The project is running remotely on the SAS server and we are using the SAS Enterprise Guide built in scheduler on our work laptops.
In order to schedule the job we open the EG project, click on the “File” menu and then “Schedule “project name” on the drop down list and it brings up the windows scheduler and we add the details for when we would like the job to run etc.
We have 3 projects scheduled in the morning and 1 in the afternoon (not all of these have the EG conditions in them).I didn't actually create the conditions, it was other user, however, in order to create these, we right click on a program in the process flow and a drop down menu appears, we click “condition” and then “add” to add a condition.
We print to a log in our scheduled jobs. I was wondering whether because SAS creates a separate “conditional logic log” for these conditions, it might be running this part on local? / or because it is in a separate log, our batch job may not be picking this up when running in batch (but we were just guessing).
we are using the SAS Enterprise Guide built in scheduler on our work laptops.
Can you let us know why the conditions are not working and why batch is not running properly?
12-07-2013 05:58 PM
You didn't give us a lot to work on. What are the symptoms? What are the return codes from the Windows Scheduled Task tool in the Control Panel?
In order for a scheduled job to run from EGuide, the laptop must be connected and on so that the process can run. Even thought the SAS is running on a remote server, the process is being launched from the laptop.