Architecting, installing and maintaining your SAS environment

SMC scheduler stops job scheduling - Wrong time to run script

Accepted Solution Solved
Reply
Frequent Contributor
Posts: 75
Accepted Solution

SMC scheduler stops job scheduling - Wrong time to run script

Currently we got problems with scheduling from SMC that uses the scheduler on HP unix. Some of our jobs runs through but pt. a lot of them is stopping of some reason. Also jobs which functioned a day ago. The scrips (log file from running .sh scripts stops contain this message ;

 

warning: commands will be executed using /usr/bin/sh

job 1458362460.a at Sat Mar 19 05:41:00 2016
ATJOB Submitted
16/03/18 06:55:00 Wrong time to run script, stopping
16/03/18 06:55:00 Flow RRRR_FFF_d exiting 0

 

Thanks in advance. Hope to hear from you if you have any clues.

 



and it occurs for jobs which can run by run now and has worked before. Do you have any ideas?


Accepted Solutions
Solution
‎03-23-2016 04:26 PM
Frequent Contributor
Posts: 75

Re: SMC scheduler stops job scheduling - Wrong time to run script

[ Edited ]
Posted in reply to JuanS_OCS

Hi Again, Thanks for your reply. We tried it. But It did not solved the problem. Then  I emailed SAS support and they told me that there was a restriction for how many jobs could be runned simultancenous on unix. It has been set up below /ets/cron queuedefs. We doubled the numbers and now the scheduler is up running 100%.

 

View solution in original post


All Replies
Trusted Advisor
Posts: 1,326

Re: SMC scheduler stops job scheduling - Wrong time to run script

Hi,

This can occurr if your machine has a different time of the time running on you at processes.

Please check the logs of at (bar/logs/at i giras) and compare with your current system time.

I expect this to be solved if you restart your at service.

Solution
‎03-23-2016 04:26 PM
Frequent Contributor
Posts: 75

Re: SMC scheduler stops job scheduling - Wrong time to run script

[ Edited ]
Posted in reply to JuanS_OCS

Hi Again, Thanks for your reply. We tried it. But It did not solved the problem. Then  I emailed SAS support and they told me that there was a restriction for how many jobs could be runned simultancenous on unix. It has been set up below /ets/cron queuedefs. We doubled the numbers and now the scheduler is up running 100%.

 

☑ This topic is solved.

Need further help from the community? Please ask a new question.

Discussion stats
  • 2 replies
  • 355 views
  • 0 likes
  • 2 in conversation