×
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?
Reason for asking:
I got a strange problem occurred to me this morning and it appears to be
cause by exception message only percolate up to the activation group
boundary. Below is what happened:
1) I recompiled/recreated a service program and during this
recompile/recreated I changed the active group of this exist service
program from *caller to be the name of the service program (Our shop
standard, not sure why).
2) A few application that uses one of the export procedure in this
service program started to fail after #1.
Those applications basically doing the callp(e) to the export procedure.
In the joblog, I notice that the service program is getting error out
when activation group is not *caller. If I change the activation group
to *caller, the service program seems to not error out due to callp(e).
thanks
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
