Re: qtemp

QTEMP belongs to the job. A web server job runs all day and services
requests from many different users. A single users requests may be
handled by different jobs (unless your doing persistent sessions and
then things are different). As far as being "accessable" it depends on
your perspective. A user would not be able to enter something in the URL
line to get at a QTEMP file since the Apache server can't be configured
to access the QTEMP library. The CGI job that created the file or any
other CGI job running in that web server job will have access to the
QTEMP file. If you use QTEMP files in a CGI app you should be very sure
they get deleted/cleared after each request or you could serve up the
wrong data to the user.  We do not use QTEMP for web apps, we do have
some apps that create a work file for each user in a regular library
with the file name unique to the user and then the CGI app references
the file associated with the user.

raul@xxxxxxxxxx 9/13/2006 7:04 PM >>>

If a CGI program creates an object in QTEMP, will it be accesible by 
other users? all web users? only same user? nobody?

Apache opens several jobs, but I don't know if each job is associated 
with each user, or if a user can open several jobs or if a job has 
several threads for each user.

It seems to me there must be a QTEMP for each job, is it so? or is it 
for each thread?