On 03/07/2010, at 9:09 PM, Dennis Lovelady wrote:
The question that leaves in my mind is how that might cause a
failure to
occur at the UPDATE statement. Shouldn't it occur at the second or
later
call to QDBRTVFD?
Not necessarily and probably not in actuality either. The call will
"work" because nothing has been trashed in QDBRTVFD. The damage occurs
in the caller's storage so no failure is likely to be noticed until
return to the caller. Exactly where the failure occurs will depend on
the structure of the calling program.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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.