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



 >> So we can just forget EXIT PROGRAM/STOP RUN and only  use GOBACK, then,
in all programs, without considering whether they are called as main- or
subprograms (or both)?

That's the basic idea.  Obviously there are performance and logical
implications of a program doing a STOP RUN when an EXIT PROGRAM was
expected, but at the lowest level, yes GOBACK will deal with the problem.

If a program is _known_ to be intended for use as a subprogram, I would tend
to still code EXIT ... followed by an "Oh sh*$" routine.  Unless you do this
(and particularly in the case of ILE COBOL and mixed language shops) you
have the potential of creating a performance nightmare and never knowing
about it.  The Run Unit (which = Activation Group for ILE COBOL) will be
going up and down like a yo-yo.  One customer we worked with back in the
early days of ILE COBOL has a subprogram that worked fine from COBOL but
when used from his RPG code took over 20 times longer to run than the OPM
version!!

Jon Paris
Partner400




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.