Some of our users use a canned application to submit batch jobs to the system.
In the background the application is using the "at" command to submit the job
along with its scheduled time. At times there is a need to submit several
batch jobs to run over night in a certain sequence but we have found that DUNIX
does not process batch jobs in a consistent manner if there are several jobs
waiting to run from the same single-threaded queue. For example, we have
submitted 3 jobs to run in succession, one at 04:00, one at 04:15 and one at
04:30 and lets say we had another batch job which was submitted earlier to the
same single-threaded queue at 03:45 and is currently active and doesn't complete
until 05:30. When 05:30 rolls around and the active job completes, there is no
guarantee as to which order the 3 pending jobs will be processed in since
their scheduled time has passed. Initially, I thought the system should take
them in on a "first-in first-out" basis but this is not the case, the observed
behaviour is inconsistent. So I am wondering if there is any reliable way to
schedule batch jobs so they will be processed in an orderly sequence? I thought
it might be helpful, so I've included the contents of my
"/var/adm/cron/queuedefs" file here:
a.1j20n60w
b.1j20n60w
#c.1j20n60w
#d.1j20n60w
#e.1j20n60w
#f.1j20n60w
We're just using the 2 queues "a" and "b".
Any advice would be greatly appreciated.
TIA,
clos_at_nhb.com
Received on Tue May 11 1999 - 03:54:39 NZST