Scott, We set this up last night and are watching the web jobs this
morning to see the effect. It almost looks like the Apache server is
changing the library list before calling the CGI application and then
changing it back after the CGI job responds. And the library list it
gets set back to is the initial list for the HTTP job. When we look at
the jobs library list it only ever shows the initial libraries but the
job log has warnings where our jobs were doing ADDLIBLE commands that
the library is already in the list except for some that we did not put
in the environment variable. Do you know if this is a correct
interpretation on our part?
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [
mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Scott Klement
Sent: Thursday, June 07, 2007 7:53 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Library list control and net.data and RPG CGI apps
Hello Nathan,
I thought the SetEnv directive would create an environment variable
that the CGI program could reference, and then possibly run code to
change the job's library list at runtime.
You're right that SetEnv is used to set an environment variable.
However, it's Apache (or, specifically, the i5/OS version of Apache)
that sets the library list.
You do not have to code anything relating to this in your CGI program,
it's done for you by the HTTP server.
But are you saying that the HTTP server uses that directive to
automatically set the job's library list, when a program in
/cgi-test/ewo is called?
Actually, in Shane's example, he used /cgi-test/ewo*, the * is a
wildcard, so any program name in /cgi-test that starts with "ewo" would
get the library list.
But, yes, it's done for you automatically...
midrange.com
