×
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.
<Snip>
There are some V5R4 APARs that may apply:
http://tinyurl.com/26xj6c
http://tinyurl.com/26httq
PTF listed for both APARs is SI28289.
<Snip>
We are missing that PTF so I will see about getting that loaded in the
morning.
<Snip>
If that doesn't help... perhaps it's a *LIBL issue. Check if you're using
*SYS naming syntax and if one of the calls is changing library list. Or
if
*SQL naming, check if one of the calls is setting SQLPATH (that's the path
system searches for SPs and UDFs).
Other than that... data types have to match SP input argument
declaration...
also, I've seen strange things with commitment control in the past and
PRTSQLINF may help here.
<SNIP>
I don't think these are the case though. The SP is doing a really simple
fetch of data into a result set. Nothing going on with changing libraries
or SQLPath. Also I have double/tripple checked that the types and sizes
match and there is no commitment control going on.
Thanks for the quick response... I see what the PTF does tomorrow.
Jack
midrange.com
