|
PASE doesn't use prestart jobs by default, but you can tell it to.
http://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/ssw_ibm_i_71/apis/qp2runpase.htm
I don't know if that is the exact link, but this has similar information.
If you go down to "usage notes" you will see:
---
QIBM_PASE_USE_PRESTART_JOBS
When this ILE environment variable is set to Y, IBM PASE for i runtime
uses prestarted jobs for child processes created by fork and for any job
started by the systemCL IBM PASE for i runtime function (to run a CL
command). You should add prestarted job entries (ADDPJE command) for
programs QP0ZSPWT (used by fork) and QP0ZSPWP (used by systemCL) to any
subsystem description that will run jobs that use this support.
---
That is the configuration I am attempting to use. I've created the
prestart job entries and I set that environment variable. It works, but it
only uses the jobs once, which really isn't the behavior we were after. We
were hoping it would use the 2 prestart jobs over and over.
--
Matt
On Wed, Jul 15, 2015 at 11:00 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
I'm not aware of PASE using prestart jobs....
Where are you getting that impression from?
Charles
On Wed, Jul 15, 2015 at 9:44 AM, Matt Lavinder <
mlavinder@xxxxxxxxxxxxxxxxxxx> wrote:
I am a bit confused on something.particular
I created pre-start job entries to handle PASE calls made in a
subsystem. I was under the impression they would be reused, but itappears
they end after 1 use. MAXUSE was left at the default of 200.how
Am I missing something? I am not sure if this is a misunderstanding of
prestart jobs work or if I am seeing behavior that is not expected.Scott
Klement had mentioned unpredictable behavior if I didn't "fork" andsetup
output descriptors. I am not sure if this falls in that category ornot.
The scripts I am running function just fine. All the jobs seem to belist
completing normally when I look at the job logs.
Thanks for any help.
--
Matt
--
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,
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.
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.