|
That implies the issue is resolved by Work Management. So again, why
would a program need to know the answer? A program should be given
inputs which tell program what to do, so why would the program need to
know "whether it's running in a 'web server' job?" if that program has
been told what to do?
Regards, Chuck
On 18 Jan 2013 12:11, Vernon Hamberg wrote:
The issue as originally formed was that server jobs are basically
batch jobs, but web server jobs behave like interactive ones. One of
the ERP vendors, as I recall, even talks about making adjustments
that will accommodate this and maybe help performance some. I don't
think those suggestions require figuring OUT the status, you set up a
subsystem description or prestart job entries or something like
that.
On 1/18/2013 12:35 PM, CRPence wrote:
On 17 Jan 2013 13:56, Jon Paris wrote:
On 17 Jan 2013 11:14, Rory Hewitt wrote:<<SNIP>>
The TYPE value for RTVJOBA returns '1' for INT jobs and '0'True - unless of course one thinks of a web app as interactive.
for everything else, I believe. I can't think that any of the
other types could be an interactive job, under any meaningful
definition of the word 'interactive' as it applies to jobs on
the i.
Which is a "meaningful" definition but admittedly not in the
conventional IBM meaning of "interactive".
I've yet to find an API that will tell me if I am running in a
web server job.
So... Suppose the answer is known, whether the program is "running
in a web server job?" What does knowing that information then allow
the program to do and\or what does knowing that information then
preclude the program from doing? Also I am curious what difference
is there between a "web server job" and any other type of job that
might be servicing requests from elsewhere [other than an
interactive display device]?
<<SNIP>>
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.