|
Hi
Prioroties - is good and bad solutions -
bad because if some job taking long time in QBATCH any other jobs which
will call after - have to waiting regardless of his high priority ....
Other things which I not sad clear -
It should works in that way :
some jobs - like printing on paper report should always not waiting for
anything - have to high priority
some jobs - should have high priority if userA called them, and small
pririority if userB called them
some user (i mean his jobs) have to have high priroty - regardles of type
of called job.
So in my opinion do something like this using only priority will be not so
easy ...
I think I need three jobqs:
1) PRINT - ONLY for printing
2) REPORTS - ONLY for reports (time consuming jobs)
3) QBATCH - for any other
Tomek
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.