• Subject: Re: Delphi stored procedures
  • From: Vernon Hamberg <hambergv@xxxxxxxxxxxxxx>
  • Date: Sun, 24 May 1998 17:34:51 -0500
  • Cc: albert.york@xxxxxxxxxxxxxx
  • In-Reply-To: <c=US%a=MCI%p=NISSAN%l=NMCHQT22-980124005039Z-69184@nmchqt24.nissan-usa.com>


At 04:50 PM 1/23/98 -0800, you wrote:
>We are trying to use Delphi to access a stored procedure on the AS/400.
>We are able to send parameters to the AS/400 program but we can't get
>any parameter values back. I have verified that the AS/400 program is
>receiving and returning the values we expect but they are not getting to
>the Delphi program. I did a communication trace and the data did get
>sent back to the PC. We have set up everything by the book (the
>parameter is defined as an INOUT string). When I look in the Client
>Access history log I see the following message: CWB011 A buffer passed
>to a system call is too small to hold valid data. 
>We are running V4R1 on the AS/400 and connecting via Client Access over
>TCP/IP and are using ODBC.
>Does anyone have any suggestions? 

Don't know 'bout Delphi, but do any of the parameters passed need to be
initialized? Or are they variable-length strings, as in VB?

Can you tell from the trace which parameter hasn't been set?


Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

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

This mailing list archive is Copyright 1997-2019 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].