Re: Question on QTEMP and CGI Jobs

Kevin,

Thanks. That's what I want to double-check. Make sure an entire call completes synchronously and has its own copy of QTEMP.

The data area is only used during the original call. We're not trying to use it across more than one call which would be problematic.

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com

------------------------------

message: 6
date: Sat, 4 Mar 2017 09:07:35 +0000
from: Kevin Turner <kevin.turner@xxxxxxxxxxxxxx>
subject: Re: [WEB400] Question on QTEMP and CGI Jobs

There is nothing special or different about QTEMP when used in a CGI thread. It's unique to the thread/job so nothing else can touch objects in there other than that thread. Obviously you cannot rely on storing a value in QTEMP on one request and retrieving it in another request because (unless you use persistent CGI) each request can go to a different thread (with a different instance of QTEMP).

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ?
On 4 Mar 2017, at 05:58, Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

We have an interesting scenario where a CGI job is using a data area in QTEMP for a temp value in a web app and there appears to be a random issue where that value gets clobbered by another job. (At least that's what we think is happening.)