Re: Question on QTEMP and CGI Jobs -- WEB400

Subject: Re: Question on QTEMP and CGI Jobs
From: Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx>
Date: Sat, 4 Mar 2017 13:52:17 +0000
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>

The app does use cookies to track a session ID.

This is for back end processing during the RPG/CGI call.

Regards,

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

message: 5
date: Sat, 4 Mar 2017 00:57:14 -0600
from: Booth Martin <booth@xxxxxxxxxxxx>
subject: Re: [WEB400] Question on QTEMP and CGI Jobs

Not an answer for you, but I am curious? Why this solution instead of a cookie on the client?

On 3/3/2017 11:57 PM, Richard Schoen 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.)

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.