You are absolutely correct.  I thought that you would see it in the log, but alas, it isn't listed.  I also took a quick look at QSYSOPR messages and don't see reference made to me holding the queue there either..........
Warmest Regards,
Richard Reeve

On Monday, December 2, 2013 1:38 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:

I tried a DSPLOG QHST but did not
see where job queue QINTER was held
or released.
guess I missed something . . .

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: Monday, December 02, 2013 10:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: QINTER job queue held

You can try DSPLOG to print then search on 'held' or 'HELD'.
Warmest Regards,
Richard Reeve

On Monday, December 2, 2013 12:27 PM, David Gibbs <david@xxxxxxxxxxxx> wrote:

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.


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].