|
> From: Justin Houchin > > I need some help. We have are QBATCH subsystem setup to only > run one job at a time. This is so that when running sales reports, only > one will run at a time (Some of the reports update files that other > reports will read, so that is why). By the way I didn't write these > report programs:-). Well this is the problem..When a report is in QBATCH > running, I have to wait for it to finish before my submitted job will > run. The reports take about 30 min. This is to long for me to wait. My > boss told me to change my submitted job to the QINTER subsystem to run. > I don't think this is a good idea, but I don't really know. Any ideas? Justin, this is a fairly standard problem - may shops require a single-threaded job queue in order to run sequential batch jobs, and often they use QBATCH for this purpose. But you can set up multiple job queues for the QBATCH subsystem. One can be set to allow multiple jobs to run simultaneously, while the other is set for single-threaded access. This way, more than one can run in QBATCH, while still having a queue that is single threaded. The downside is that your jobs will consume some of the resources in the QBATCH subsystem, slowing down the other jobs. But this is preferable to running in QINTER, where the default job characteristics (such as TIMESLICE) are generally set for interactive jobs, not batch jobs. Joe
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.