Item Subject: Message text
Randy writes:
> Gavin writes:
> >But... THIS DOESN'T WORK! A :PAUSE of 65 seconds apparently does not
> >guarantee that we have gotten to at least 23:01. At least on this
> >customer's system it frequently fails to do so.
>
> Is your customer's system, by any chance, a multi-cpu system?
 
Nope. This is just an ordinary 957. I thought about the multi-cpu
problem and checked this earlier.
 
I *suspect* that a pause of 120 seconds would be needed to guarantee
that things would work right (on a single CPU system), since it looks
as though the implementation of Scheduled Jobs might be be suffering
from an aliasing problem between the units the user specifies in
(minutes) and the units that the timer facility (or whatever) uses
internally (milliseconds?).
 
G.