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



I did not understand things to be this way, Leif.  What the docs *used to* say 
was that the first COBOL program in the stack created the run unit.  Once the 
first COBOL pgm in the stack ended (no matter how) the run-unit was deleted.  
Therefore Brian's concern was valid.  Furthermore, it wasn't until the feature 
Jon referenced was in place that an option other than a "run-unit starter" 
program would prevent the run-unit from being deleted.

Disclaimer - I haven't been a /400 COBOL guy in about 7 years.

Michael Polutta
Atlanta, GA


> From: Jon Paris <Jon.Paris@Partner400.com>
> > Brian's concern is valid, but the COBOL compiler now provides an
> alternative
> > to the "wrapper" method.  You can now:
> >
> > Exit Program and Continue Run Unit.
> >
> > Which will keep the run unit intact and avoid the overhead he mentioned.
> >
>
> But, Jon, it has always been like that.
> EXIT PROGRAM leaves the run unit alone (and all variables and
> open files etc in their current state). Why do you say "You can "now".?
>
> _______________________________________________



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.