×
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.
On Oct 7, 2010, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
What it
_should_ do (IMHO) is reactivate the *SRVPGM, and use a new pointer...
but it makes no attempt to do that, it just tries to call the old
pointer, and fails:
I think the problem with this Scott is that it would require that a
test be made of the pointer before each and every usage of it and then
re-resolving if needed. Otherwise how could it know that the Service
Program has gone bye-byes? Doing that would kinda fly in the face of
what these bound calls were designed to do though - namely be as fast
as possible with the kind of checking done on dynamic calls stripped
away.
Not sure how much it would "cost" or if the problem occurs frequently
enough to warrant such a change.
Could it be implemented manually? I haven't time to check but if there
is a surfaced MI instruction that can check the validity of a
procedure pointer, then if you used a procedure pointer for the calls
- it could be tested and re-resolved using the APIs when needed.
As you, I and Larry have all said though - the error should never have
reached the point where it destroys the AG anyway.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
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
