Re: exit the program from the subprocedure -- RPG400-L

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

Subject: Re: exit the program from the subprocedure
From: "Buck" <buck.calabro@xxxxxxxxxxxx>
Date: Wed, 18 Jun 2003 13:02:28 -0400
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

> Buck:  Would the method mentioned below still work if I need
>to exit the program with *inlr off?  Another word, I need the storage
>to stay as it was if the program happen to be called again.

Good question.  I don't know the answer (never did it), but I can guess.
Sending an escape message up the stack terminates 'this' program.  I doubt
any memory is reclaimed but it should be easy enough to test.
Unfortunately, I am tied up right now.  It would be great to hear the
results of your testing!
  --buck

As an Amazon Associate we earn from qualifying purchases.

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.