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