Good News Everybody!
The new search engine is LIVE!
Please report any problems to david (at) midrange.com.
|
That's why I added the etc... I know that all variables & indicators are reinitialized amongst other functionality. I was just pointing out that you could emulate *INLR .... but prefer not too ;-) Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx]On Behalf Of Barbara Morris Sent: Monday, July 25, 2005 3:44 PM To: rpg400-l@xxxxxxxxxxxx Subject: Re: Ending a program from within a procedure Holden Tommy wrote: > > 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 > You could use CLOSE *ALL. Using explicit CLOSE operations only handles part of what *INLR=*ON does. Ending the main procedure of a module with LR on also causes the global variables to be reinitialized on the next call to the main procedure.
This mailing list archive is Copyright 1997-2026 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.