×
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 am having trouble calling an ILE stored procedure that is part of a
service program from an SQL Function.
Short story is that the results are inconsistent. Sometimes it will
correctly determine whether the customer is a store, sometimes not, and
sometimes it gives a decimal data error. The decimal data error always
occurs where the parameter is moved to the key field for the chain. The
ILE stored procedure works every time when called from RPG. It act as if
the parameter placed in a memory location that the store procedure does
not access correctly so that sometimes it pick up the correct number and
is ok and other times it either gets part of a number or none of it. The
following error message shows that the external procedure was found and
executed and failed inside the RPG code. So this does not appear to be a
signature mismatch.
Message . . . . : Application error. MCH1202 unmonitored by VALID at
statement 0000008800, instruction X'0000'.
Cause . . . . . : The application ended abnormally because an exception
occurred and was not handled. The name of the program to which the
unhandled exception is sent is VALID VALIDE AMIASTORE. The program was
stopped at the high-level language statement number(s) 0000008800 at the
time the message was sent. If more than one statement number is shown,
the
program is an optimized ILE program. Optimization does not allow a
single
statement number to be determined. If *N is shown as a value, it means
the
real value was not available.
The store procedure code follows. I have removed the file spec for
lmllst01 and comments:
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.