Re: QTEMP objects and Different Users on the Same Job

Yes.. I agree with Nathan. No reason why in specific cases like web server
instances that QTEMP should act any different than any other job.

It's just a unique situation that we ran into regarding object authority.
It was easily remedied with one simple command added at the beginning of
the job.

The data in this example is of no consequence and is just different each
time it's run. It's not data that needs to be saved, protected, or
hidden. Just your everyday general purpose temporary file in QTEMP. :)

Brad
www.bvstools.com

On Tue, Mar 22, 2016 at 11:47 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Seems to me that the OS should clear QTEMP when it resets the job for the
next request.

What do you mean by the OS resetting the JOB? CGI JOBS just return to a
message-receive wait state after completing requests.

The problem I see with having clear it yourself at the end of your

request

is that it's possible that something goes wrong and your cleanup code
doesn't run.

CGI JOBS that fail are automatically ended, and don't handle new requests.
A new JOB would be spawned. Clearing files could be the first step in the
process, rather than the last.

I suppose one should be using ILE and the Register Activation Group Exit
Procedure (CEE4RAGE) API to ensure that you cleanup after yourself...

Seems to be unnecessary.