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


  1.  Home
  2. MIDRANGE-L
  3. August 2014

Re: SQL performing a CALL with parms...



we may have created a stored procedure....
but I can't find the SQL that created it!
(I see this program is in QSYS2.PROCEDURES)
is there some way to back into the source?



On 8/27/2014 2:55 PM, Gqcy wrote:
we are executing a one line SQL script:

CALL SYS001C PARM('parm1', 'parm2')

the parms are varying length on the input sql...

on the CL I have identified parm1 as 18 char (was 10 char), and parm2 as
64 char (was 32 char).

we have recently been changing the CL to accept different length parms,
and it appears that we are still receiving the old lengths...
and....
won't accept the longer length parms...
I get a "conversion error" 9 -- Truncation when mapping a variable or
constant to a character or binary parameter on a CALL statement, or when
using a character or graphic variable in a GET DESCRIPTOR or SET
DESCRIPTOR statement.



on my dumpclpgm:


&parm1 *CHAR 18 'parm1 parm2val'
&parm2 *CHAR 64 'parm2value '






As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.