×
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.
You could use the QleActBnd API to re-resolve a pointer to the called program each time. In that case, you'd have to define FOO as being based on a procedure pointer.
Rory
--- Original Message ---
From:"James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Sent:Wed 8/12/09 11:23 am
To:rpg400-l@xxxxxxxxxxxx
Subj:Guaranteeing re-resolution on CALL statements
I have a situation (in an update utility) in which a statement of the form
C CALL FOO
C PARM BAR
. . .
is called repeatedly for different "elements" of the update. It can,
under certain circumstances, result in FOO itself being replaced,
producing a MCH3402 exception on subsequent iterations.
Anybody know of an easy way to guarantee re-resolution of FOO to the new
version, if it gets updated?
--
JHHL
(wishing I could ANSWER somebody's question for a change!)
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Guaranteeing re-resolution on CALL statements, (continued)
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
