|
Great advice so far - or you could use jobq QTXTSRCH. How about QPGMR ? - just don't let your pointy-haired boss do what ours did one evening. Submitted a series of run-alone report jobs, all using the same file, to a triple-threaded jobq of ours by mistake. To prevent them all running at once, he had the ingenious idea of doing a WRKSYSSTS, and changing the Max Act entry for that shared pool to 1. There was quite a backlog by the morning, & several people releasing released jobqs in frustration. You can, you see, assign any amount of job queues to feed through any (started) subsystem, admitting x jobs at a time, but the amount of jobs active at one time in that pool can be altered too. I would recommend setting up a job description especially for certain kinds of jobs, which states which jobq the jobs go to, and using that for yourself - or a group of developers - whoever shouldn't block QBATCH jobq. Bear in mind also that when removing a jobq entry from a subsystem description, you may need to end & restart the sbs to make the change apply. And always check all jobds on the system for references to that now incative jobq ! Fiona fiona.fitzgerald@notes.royalsun.com
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.