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



If it's running in ACTGRP *NEW then yep it could be your problem.
Generally I just hate using *INZSR....(just one of my not so favorite
"left-overs" from the RPG II days.IMO they should scrap it...) 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert
Sent: Monday, November 28, 2005 4:55 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: INZSR weirdness

I've just converted the prototype of my SQL project so 
that instead of looping on The Cycle, initializing SQL at 
the beginning of execution, setting LR on, and shutting 
down SQL at the end of execution, it now loops with 
DOxxx-loops and RETURNs with LR off, and SQL still 
connected.

It works beautifully the first time it's called in a 
terminal session. It crashes and burns the second time.

So far, I've tracked down the problem to the INZSR getting 
called in the second and subsequent invocations, even 
though LR was never set (and I've verified in the ILE 
Debugger that it was never set).

According to everything I've read, and everything I've 
ever heard about INZSRs, they're not supposed to execute 
if the program is being called for a second or subsequent 
time in a job, if LR wasn't set in the previous 
invocation.

Can anybody shed any light on this puzzle?

Could it have anything to do with the activation group the 
program is running in?

--
JHH

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.