×
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 Jan 27, 2010, at 12:31 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
The code works fine. What I don't understand is why ForceRead has a
value. When I run in debug I would expect the evaluation of the
ForceRead parameter to not be addressable because it wasn't passed.
Instead it contains the value from an earlier call that did pass the
parameter. Is it that once the parameter is passed the procedure
retains that address in memory and therefore the value of that
parameter?
The fact that you saw your old data was basically a matter of luck and
timing. It could have been a pointer to any old parm previously passed
by a call with that many parms (or more). Luckily for you you were
defending correctly (i.e. checking %parms) and not attempting to
update the parameter. I've seen some really nasty DB corruption caused
by folks who used and updated more parameters than they received -
assuming that it would blow up if the parm wasn't passed. Really bad
assumption.
This thread
http://archive.midrange.com/rpg400-l//200301/msg00210.html
dealt with the topic. I've also written on it including sample code to
demonstrate what's going on under the hood, but I can't find the
reference right now.
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
