Or, for the old-timers, QS36EVOKE. :-)
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger
Sent: Thursday, August 28, 2014 6:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: running batch jobs from QINTER
+1 for QUSRNOMAX. When it absolutely, positively has to run NOW and not
hold anyone else up.
I use it all the time.
Date: Thu, 28 Aug 2014 15:59:22 -0500
Subject: Re: running batch jobs from QINTER
Never a good idea to run batch jobs in QINTER - the characteristics of
the *INTER machine pool are that the jobs get a lot more priority than
they should for batch work.
Instead, use JOBQ QUSRNOMAX - there is no limit to the jobs that can be
run through there - and it's on the system for this exact purpose.
And hardly anyone else would know about it!!
On 8/28/2014 3:42 PM, Hoteltravelfundotcom wrote:
Is there any performance issue at all
running batch job in QINTER session. the job will take about 20 seconds
I would make it in a loop to run every few minutes. until I complete the
view that would negate the need for this run.
I would have it close itself every night and a scheduled job kick it off
The reason I dont want to put this in batch is because, the batch queues
are single threaded so you can't hold up the others. and there are jobs
that need to run before the daily IPL - if they dont the machine won't
up. So am very afridai to mess around there.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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