We're guilty as charged.
On the other hand, these jobs more similar to inter-active
because they are of "order entry" jobs where a customer
order is copied from one system to another using an interface
created just for this purpose.
As to creating the additional job queue, does not fall
within my area, but I will suggest we do as you have
so as to avoid this in our future.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Monday, December 02, 2013 10:27 AM
To: Midrange Systems Technical Discussion
Subject: Re: QINTER job queue held
On 12/2/2013 11:22 AM, Gary Thompson wrote:
We are researching an issue that caused us some grief last Friday,
November 29th where job queue QINTER was held for some time.
Why would anyone be concerned about the QINTER job queue being held? Batch jobs shouldn't be submitted to the QINTER job queue.
A long time ago (a different lifetime, almost), I got in some hot water with the data entry manager because I put the QINTER job queue on hold. The data entry people were submitting their print jobs to QINTER because their jobs were far more important than anything else that was happening in the company <sarcasm implied/>.
I resolved the issue by giving the data entry department their own subsystem and job queue's, so they could get their print jobs done quickly without effecting the rest of the company.
IBM i on Power Systems: For when you can't afford to be out of business!
I'm riding a metric century (100 km / 62 miles) in the 2014 Chicagoland Tour de Cure to raise money for diabetes research, education, and advocacy. Sponsor me by visiting http://archive.ridewithdavid.com
. Any amount is appreciated.
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 at http://archive.midrange.com/midrange-l