Stan replies,
 
>Gavin has evidence that a job that starts at 23:00, does a pause 60,
>and then does:  stream thejob;at=23:00
>could *still* end up being scheduled immediately (with the CIWARNing
>being issued about an "AT" time being <= now).
 
>I.e., it ought to work ... but doesn't always.
 
Hmmmmm.....makes one pause to think...How about if your job paused
for 61 seconds, then?
   !pause 61
   !stream me;at=23:00
This is assuming that the job takes less than one second of wall
time to run.
 
For the really paranoid, (who, me!?) you could also place a time check inside
the job that has been streamed:
 
   !job  me,mr.paranoid
   !
   !setvar sched_hour 23
   !setvar sched_minute 0
   !setvar sched_minutes sched_hour * 60 + sched_minute
   !
   !comment   If the current time is < the sched time, then abort
   !comment   and re-stream for later.
   !setvar current_minutes hphour * 60 + hpminute
   !if current_minutes < sched_minutes then
   !   stream me;at =!sched_hour:!sched_minute
   !   eoj
   !endif
 
(Note:  Yes, the stream command will accept 23:0 as a valid time!)
\KenR
--------- "This is dragging on longer than I thought."