Re: Creating an SQL function from a service program -- MIDRANGE-L

× 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.

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 01/09/2018
10:29:52 AM:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 01/09/2018
10:26:28 AM:

It would seem your service procedure is expecting zoned-numeric
parameters and your SQL stored procedure is sending packed-decimal
parameters.

I should note that my reading of the SQL manual gives me to
understand that NUMERIC and DECIMAL are the same format -- packed

decimal.

I don't know of a way to specify zoned-numeric format in an SQL

parameter

other than to send it as character -- then the receiving procedure will
treat it as zoned-numeric.

I rechecked the SQL manual and it appears I was thinking of a
different dialect of SQL which stated that NUMERIC and DECIMAL were
interchangeable. The IBM i 7.1 manual states that NUMERIC *is* for
zoned-decimal format. So, I would set a service entry point on your
service program from RDi and check the hex values of the actual data that
is being passed from the stored procedure.

Sincerely,

Dave Clark

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.