Re: Question on QTEMP and CGI Jobs -- WEB400

Subject: Re: Question on QTEMP and CGI Jobs
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Sat, 4 Mar 2017 08:52:44 -0700
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

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.)

I don't see any way a qtemp object could get clobbered by another job. As
others have indicated the request-response cycle is synchronous. But since
a single CGI job can have an unlimited number of programs active in the
same job, it seems theoretically possible that one of them could clobber a
qtemp object due to CPU time slicing. Perhaps unlikely, but I'd still steer
away from using qtemp in CGI jobs.

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.