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



You can avoid using *INLR....by explicitly closing all files/ODPs etc THEN 
using return....

But I'd rather use one line of code *INLR=*On instead of

/free
   close file1;
   close file2;
   close file3;
   return;
/end-free

Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
Sent: Monday, July 25, 2005 2:44 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Ending a program from within a procedure


On 7/25/05, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx> wrote:
> 
> > I generally use a Terminate subroutine with the last 2 lines
> > being *INLR=*On & return...
> 
> I like that idea better.
> 
> Turning on LR at the beginning just doesn't seem right. Reminds me of
> clicking 'Start' to end windows.
> 
> <g>


Perhaps by writing code using this technique, my software might sell 
1/1000000 the copies Gates has sold? In that case, it's not so ugly ;-)

I see what you mean though. I have gotten used to issuing '*InLR=*On;', so I 
don't think about it much. It would be nicer to not have to utilize the LR 
indicator if you have all full procedural files. Or perhaps it should be an 
H-Spec... LRObsolote(*Yes). Or UseLR(*No)...

How about LRObsoleteIAmInThe21stCenturyForGodsSake(*Yes) ;-)



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.