I'd be concerned that it'd be possible that the job could start before
it gets moved. Unless you default to placing the jobs on a queue that
is not attached to a SBS.


On Thu, Aug 6, 2009 at 10:45 AM, Vern Hamberg<vhamberg@xxxxxxxxxxx> wrote:

Search in google for "job notification exit" and you will find something
at IBM - it lets you name a data queue to which messages will be placed
when jobs hit various stages in their running. One of these is being put
on a job queue. You would have a never-ending-program to wait on that
data queue, then, when a job i put on a job queue, you can change that
job to go to a different job queue. You would need some kind of control
file or hard-coded set of IF or SELECT to decide which way to go.

HTH - that was just a quick thought

Tomasz Skorża wrote:
Good morning/evening

I would like to ask if you know any solution how we can divide and send
jobs to other job queues depend of type of job (not depend of user
1 - every long_time_consuming reports which is not important is going to
queue - SNAIL :-)
2 - report which have to be done ASAP - to queue - RABBIT
3 - any other batch jobs to queue QBATCH

I thinking about some exit point which will be recognize called
jobs/program and using some rules will change default QBATCH to other.
Is it possible?



__________ Informacja programu ESET NOD32 Antivirus, wersja bazy sygnatur wirusow 4312 (20090806) __________

Wiadomosc zostala sprawdzona przez program ESET NOD32 Antivirus. lub

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].