I doubt this has anything to do with activation groups, but even if it
does you have a larger problem.
CGI is different than 5250. When you are logged in via 5250 you have a
single job that services your session. But with CGI the web server has
a pool of jobs that service users and every time you send a request you
could potentially use a different job.
Basically you could think of it as every time you send a new request
your programs start over from scratch. As far as I know there is no way
to associate a server job with a specific client.
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Rob Dixon
Sent: Tuesday, January 06, 2009 7:44 AM
Subject: [WEB400] Persistent CGIDEV2 problem
I am using CGIDEV2 (in persistent mode) for the first time and thought
I was making reasonable progress but have now run against a problem for
which I need help, although I am sure that it has been solved many times
My cgi program is RPGLE and is a request processing program (I will call
direct database access but calls a second program (I will call it MAIN).
This handles business logic and reads records and passes them back to
RPP which displays them using 5250 or CGI. In CGI mode, the first call
RPP of MAIN works OK and the records are displayed by RPP using
When I type something on my HTML display, the RPP is reactivated
so my Handle is presumably OK and I can read what I typed using
ZhbGetInput. However, when RPP calls MAIN again so that that program
retrieve the required records, a new instance of MAIN is called. I am
that in the first call of MAIN I did not set on LR and the mechanism
fine in 5250 mode I imagine that this has something to do with
Can anyone help please? I have tried compiling MAIN with the same named
activation group and binding directory as RPP but this did not help.
This mailing list archive is Copyright 1997-2019 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