×
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.
> Does any one know if exception message's percolation process only
> percolates message up to the activation group boundary or it always
> goes up the call stack without considering activation group boundary?
Percolation of error messages stops when it gets to a "control
boundary". In ILE, control boundaries are intimately linked to
activation groups. Basically, whenever you make a call that crosses an
activation group -- the first procedure in the new activation group is
a "control boundary".
IBM explains this pretty well in the ILE concepts book. See chapter 3
("ILE Advanced Concepts") under the topic entitled "Control Boundaries".
There's a nice illustration (figure 22) that helps clarify where the
control boundaries are.
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.
midrange.com
