×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Our RUNADEJOB starts at 2:25 AM.
Today we found 7 copies of the JOBSCH job running...
Not good... The reason we discovered is that the job we run to perform the
clock adjustment for "Spring Forward" and "Fall Back" also had a call to
RUNADEJOB. I assume the thinking was that the RUNADEJOB would get skipped
during the "Spring Forward" time adjustment when the clock changes from 2:00
to 3:00, completely skipping 2:25 AM...!!!
I've suggested that this is definitely not a good idea for the "Fall back"
option since it creates the multiple JOBSCH problem but then the question
becomes, what about "Spring Forward"...? Will it or won't it run our 2:25
AM RUNADEJOB scheduled entry...?
OUR RUNADSJOB is launched at 5:30 AM... How does the scheduler know that it
is not supposed to run the 2:25 AM RUNADEJOB scheduled entry right away...?
When the Machine Manager "wakes up" every 10 minutes to see if anything is
"ready" to run I have to assume it limits the past due time horizon, but
what is the limit...? Is it just 10 minutes...?
Does anyone know for sure...?
Thanks.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
