Prestart jobs were created to handle communications requests from some outside source. So when a communication request comes in, there is always an open job waiting to process it. The communication request would come in, get processed to completion and that is one use. If the threshold number of jobs is servicing a communications request, additional jobs are started so there are a sufficient number waiting to handle additional requests, up to the max. Once a prestart job services a specified number of communications requests, it ends. This allows the number of active prestart jobs to slowly die down as the volume of communications requests decrease. The nice thing about prestart jobs is that they restart themselves if one crashes, so there is always something waiting on a communications request. If you have no communications request coming in, you will never have more than the initial number of prestart jobs active, and the active ones will never end. A communications request is one that enters the subsystem via a communications entry.
Some people use prestart jobs to process things other than communications requests. For example your data queue example. Programs still restart themselves if something goes wrong, but no additional jobs are started, and programs do not end on their own because they are not processing communications requests.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----Paul Nicolay <paul.nicolay@xxxxxxxxxx> wrote: -----
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
From: Paul Nicolay <paul.nicolay@xxxxxxxxxx>
Date: 09/13/2016 11:04AM
Subject: Re: Prestart jobs... how does it work ?
Hi,
But that defies the idea of the whole prestart job stuff.
You're setting the initial number according to your needs manually... fine, but what's the purpose of additional jobs if it doesn't do anything with it ?
For QZDASOINIT etc this works fine, but how do they do it ?
Kind regards,
Paul
________________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, September 13, 2016 16:07
To: 'Midrange Systems Technical Discussion'
Subject: RE: Prestart jobs... how does it work ?
Paul:
Generally we set the number of prestart jobs to a number that provides the
service level needed for that job. For instance, it might be OK to wait for
100 queue entries to be processed over a period of time; then again it might
be imperative that they get processed very quickly. So I would either set
the number of jobs at 3 as you have done, or bump that number up so that I
have sufficient numbers of listeners to handle the load. Now the memory
management and activity levels for those jobs can be set so they process
properly. (works similarly to how many CGI jobs have to be running for the
Apache Server to process too)
I agree with Kevin, what does DSPACTPJ show?
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kevin
Bucknum
Sent: Tuesday, September 13, 2016 8:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Prestart jobs... how does it work ?
Also - when you are hitting with with 100 entries, what does DSPACTPJ show?
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul
Nicolay
Sent: Tuesday, September 13, 2016 8:32 AM
To: 'Midrange Systems Technical Discussion'
Subject: Re: Prestart jobs... how does it work ?
Hi Jim,
This is the PJ definition;
Program . . . . . . . . . . . . . . . . . . . . : TST005CL
Library . . . . . . . . . . . . . . . . . . . : PAULN
User profile . . . . . . . . . . . . . . . . . . : QUSER
Job . . . . . . . . . . . . . . . . . . . . . . : TST005CL
Job description . . . . . . . . . . . . . . . . : *USRPRF
Library . . . . . . . . . . . . . . . . . . . :
Start jobs . . . . . . . . . . . . . . . . . . . : *YES
Initial number of jobs . . . . . . . . . . . . . : 3
Threshold . . . . . . . . . . . . . . . . . . . : 2
Additional number of jobs . . . . . . . . . . . : 2
Maximum number of jobs . . . . . . . . . . . . . : 10
Maximum number of uses . . . . . . . . . . . . . : 5
Wait for job . . . . . . . . . . . . . . . . . . : *YES
Pool identifier . . . . . . . . . . . . . . . . : 1
Class . . . . . . . . . . . . . . . . . . . . . : QBATCH
Library . . . . . . . . . . . . . . . . . . . : QSYS
Number of jobs to use class . . . . . . . . . : *CALC
Class . . . . . . . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . . . . . . :
Number of jobs to use class . . . . . . . . . : *CALC
Thread resources affinity:
Group . . . . . . . . . . . . . . . . . . . . : *SYSVAL
Level . . . . . . . . . . . . . . . . . . . . :
Resources affinity group . . . . . . . . . . . . : *NO
The 5 uses only was just something to test to see if it works.
But you state that it works, do you mean that; something (the OS ?) is
starting additional jobs for you (apart from the initial ones) and based on
what ?
Kind regards,
Paul
________________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Jim
Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, September 13, 2016 15:15
To: 'Midrange Systems Technical Discussion'
Subject: RE: Prestart jobs... how does it work ?
Can you post the prestart job entry and job description?
I think your jobs should stay in DEQW rather than PSRW status. PSRW implies
a multithreaded job wait rather than a more traditional job.
We do this all the time and don't have any issues.
Why kill the job after 5 uses? It would seem to be overly expensive to
constantly be creating new prestart jobs.
--
Jim Oberholtzer
Agile Technology Architects
--
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,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
--
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,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
--
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,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
