Re: Prestart jobs... how does it work ?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

What you're missing is something to tell the system there's work for your
pre-start job to do.

This is a "work request".

PSWR is Program Start Request Wait.  The manual mentions the following...A
Program Start Request (PSR) is an architected way for SNA clients to
connect to an SNA server. When a prestart job is set up to handle PSRs, the
external state of the job is in PSRW (Program Start Request Wait).

Prestart jobs are also used for IBM-supplied TCP/IP servers, most notably
the host servers. These prestart jobs accept work via internal interfaces
and PSRs are not used. However, prestart jobs that are waiting for work,
even if they are not using PSRs, still show a PSRW state.

I'm guessing that the "internal interfaces" are the spawn() or spawnp()
APIs with the SPAWN_SETPJ_NP flag set: If this flag is set ON, spawnp()
attempts to use available IBM® i prestart jobs.

But I don't know for sure.

Charles


On Tue, Sep 13, 2016 at 11:04 AM, Paul Nicolay <paul.nicolay@xxxxxxxxxx>
wrote:

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