Re: Question on QTEMP and CGI Jobs

arhh

it gives you the QZSRCGI jobnumber and if any objects in QTEMP is left with
a lock

The most pausible reason to such error is that there some where is a
program that
originally had only one exit like

wrtSection('*fini');
cleanUp();
return;

Then someone changes the program so it know has two exit points where the
first is the
original but the second misses the cleanUp() thus leaving any objects i
QTEMP as is for
the next program



On Sun, Mar 5, 2017 at 5:55 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

The trick is this appears to be randomly occurring, so I've been told, so
a an additional logging table may be in order so we can log the errors and
research when one is reported again.

Since there are only a handful of calls in one program I plan to recommend
that they do some logging of those calls and variable or data area values
until they can track the root cause.

Also since there are only two of these data areas, moving them into our
internal web session table would also be a good direction.

What info would DSPJOB give beyond the actual job name I'm currently in
and other stack info ?

Just trying to understand how this helps me debug the contents of a data
area or other variables.

Thanks.

Regards,


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

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

message: 7
date: Sun, 5 Mar 2017 11:20:15 +0100
from: Henrik R?tzou <hr@xxxxxxxxxxxx>
subject: Re: [WEB400] Question on QTEMP and CGI Jobs

Richard

if you know the programs that causes the problem put a call to CL as first
statement in the RPGLE program
it should give you the info for each call you need ...

PGM

DSPJOB OUTPUT(*PRINT)
DSPLIB LIB(QTEMP) OUTPUT(*PRINT)

ENDPGM


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