× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I’ve recreated all my CL programs to run in QILE. This could be a problem
in the future as the shop has almost no programing standards at all. If
someone else compiles one of the programs then it will run in the DFTACTGRP.



Sending and receiving JSON data from Postman :



StartCGI not specified

request http 1 1300 ms

request http 2 200 ms



StartCGI 1 specified

request http 1 2200 ms

request http 2 189 ms



This causes 2 CGI jobs to be created





StartCGI 1 specified with HotBackup off

request http 1 359 ms

request http 2 220 ms



Only one CGI job is created.



So it looks like the lag on the first request is due to the HotBackup CGI
job being started.



So, how can I speed up my first request with StartCGI and still have
HotBackup on ?

Or maybe the question should be what's the point of StartCGI when HotBackup
on (by default) is causing another job to be initialized at the first http
request, thus losing all of the benefits of having a CGI job running before
the first call?









*De :* Dave <dfx1@xxxxxxxxxxxxxx>
*Envoyé :* mercredi 9 mars 2022 19:22
*À :* David FOXWELL <ext.dfoxwell@xxxxxxxxxxx>
*Objet :* Fwd: [WEB400] Fwd: Fwd: StartCGI bug?





---------- Forwarded message ---------
From: *Nathan Andelin* <nandelin@xxxxxxxxx>
Date: Wed, 9 Mar 2022, 17:08
Subject: Re: [WEB400] Fwd: Fwd: StartCGI bug?
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>



If I understand correctly, your call stack activations are shifting back
and forth between ILE and OPM when you compile your CLLE with
DFTACTGRP(*YES). I'm not sure what that does precisely, but I would try to
avoid that. Stick with ILE throughout the call stack. Try creating your
CLLE with CRTCLMOD and CRTPGM ACTGRP(*CALLER).

On Wed, Mar 9, 2022 at 6:57 AM Dave <dfx1@xxxxxxxxxxxxxx> wrote:

The initial program is a CLLE compiled to run in the DFTACTGRP. All the
RPGLE run in the same group I believe with the directive dftactgrp(*no)
actgrp(*caller)




From: *Nathan Andelin* <nandelin@xxxxxxxxx>
Date: Tue, 8 Mar 2022 at 16:28
Subject: Re: [WEB400] Fwd: StartCGI bug?
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx





After reading about CgiInitialUrl, I’m wondering if the lag
I’m noticing is actually because of an activation group being initiated
on
the first call as described in the manual for CgiInitialUrl.


What activation group are you using (*NEW, *CALLER, NAMED)?
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
------------------------------

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.