topic Re: Scheduled Job stops after 30 minutes in Administration and Deployment

Scheduled Job stops after 30 minutes

SAShole — Mon, 08 Jun 2020 14:56:12 GMT

I have a driver program that calls other programs like this:

%include "\program1.sas";

%include "\program2.sas";

....

%include "\program49.sas";

After thirty minutes any remaining programs never get run. Any ideas on what may be causing this or how I might begin to troubleshoot?

Thanks!

Re: Scheduled Job stops after 30 minutes

Kurt_Bremser — Mon, 08 Jun 2020 15:35:26 GMT

Do you run the "driver" program from the commandline or the scheduler?

Re: Scheduled Job stops after 30 minutes

SAShole — Mon, 08 Jun 2020 15:50:58 GMT

I have the Driver_Program.sas set to run on the scheduler. I may have misunderstood your question however. I do not run the program interactively.

Re: Scheduled Job stops after 30 minutes

AnandVyas — Mon, 08 Jun 2020 16:28:39 GMT

What scheduler are you using? Is there a time-out set?
Any logs of the original Driver program?

Re: Scheduled Job stops after 30 minutes

Kurt_Bremser — Mon, 08 Jun 2020 16:50:07 GMT

Then it's probably not an issue of your interface disconnecting (or being disconnected). As a next step, get ahold of the log and inspect it, and see where it ends.