Re: Question on QTEMP and CGI Jobs

Lets be clear of timeslice.

the timeslice origins from the *CLS object and is set to 2000ms for
Interactive jobs and 5000ms
for batch jobs - these values has not been change since the first AS/400 B
series.

The timeslice is transfered to the JOB and can be read in any JOB's run
attributes and it may
be changed by a CHGJOB TIMESLICE(50) in other words it is bound to the
QZSRCGI JOB and
not the program that the job runs.

What happens is that the QZSRCGI job is trown out of the core if the time
slice i reached so the
core can service other jobs in the job pool. It wasn't so one job that
looped would bring the
whole system down.

Now 2000ms is extreme long time in todays terms to allow a job to own a
core and if a job takes
to many resources from others reducing the timeslice given to the job is a
good place to start.

Especially QPASE programs can be a pain - none.js buffers everything or if
programmed
wrong will never go into an EVTW waiting for slow memory or disk I/O.

When i say programmed wrong in regards to node.js it is mainly because a
programmer may
cause node.js 4 different JIT compiles to go bananas and use all node.js
resources to recompile
code in the middle of the execution because it flips back and forth between
executing on baseline
instructions and optimized code and if not proberly coded it will decompile
optimized code back to
baseline and then try to optimize the code again. If the javascript code
that causes this is inside
a loop you can imagine what happens.

On Sat, Mar 4, 2017 at 10:29 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

I agree that one is subtle.

Nobody becomes good without a few fumbles.

I just happen to fumble a little eless these days after 29 years in the
industry :-)

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
---------------------
Subject: Re: Question on QTEMP and CGI Jobs
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
Date: Sat, 4 Mar 2017 16:13:44 -0500

I find that a lot of RPGers who modify/write CGI programs are completely
unaware that the jobs are reused. It is an easy trap to fall into when you
use a test setup (say on a non-std port) and nobody else is dong anything
much. The result is that you can easily slip into your old 5250 habits and
start assuming that stuff in the job will just be there.

This is one of many reasons why I have often said that it is far easier to
teach web programming to an RPG II or CICS programmer than it is to
somebody who has never done anything except RPG in an S/38 style.

Nothing is dangerous when used "properly" - I guess you are lucky enough
to only work with people who do things properly!


Jon Paris

www.partner400.com
www.SystemiDeveloper.com


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.