And I'm very glad that CGI jobs don't do a kind of reset after each
request. In our shop we load a couple of 'handler' serviceprograms at the
first request, and they stay active in named activation groups until the
CGI job ends or when they are ended explicit. And we like that approach for
performance reasons.

Regards,
Arco Simonse

Op dinsdag 22 maart 2016 heeft Nathan Andelin <nandelin@xxxxxxxxx> het
volgende geschreven:


And perhaps CGI jobs
are a bit different that an OS prestart job.


Yes, that's right. CGI JOBS are not the same as prestart JOBS. CGI JOBS
remain active - and visible from the WRKACTJOB command. They just go into a
wait state, until an HTTP server thread decides to forward another request.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx <javascript:;>
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx <javascript:;>
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx <javascript:;> for any subscription
related questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.