×
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.
I think Rob is likely correct.
I put MODIFIES SQL DATA on all SQL functions and procedures, because when I
make an SQL component I don't want to try and predict the future in terms
of what other types of objects are in the call stack when I call said
object in the future. I may only need to call an SQL object today in a
read only call stack, but down the road I may want to call the same object
in a call stack that is modifying data. That exact scenario happened to me
about 5 times until I decided to switch to consistently using MODIFIES SQL
DATA. Overkill perhaps, but I no longer see those types of errors.
Mike
date: Mon, 13 Feb 2017 10:04:57 -0500
from: Rob Berendt <rob@xxxxxxxxx>
subject: Re: Stored Procedure returning result set
I take it this RPG programs calls another sql which has the READS SQL DATA
set on it?
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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
