MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

Re: RPG integer vs SQL integer.



fixed

Rob

It looks as if the 2 SYSASP field may have different definitions - the qualified one vs the unqualified one.

HTH
Vern

On 7/22/2014 6:47 AM, rob@xxxxxxxxx wrote:
No, that's a very valid question.
When run in debug the RPG program clearly shows the value.
SYSASP = 22500008
Notice, only 8 digits used?
I'm supposing the error shows up when the stored procedure handles it but
I've not got a good handle on how to debug that.


Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: John Yeung <gallium.arsenide@xxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 07/21/2014 05:37 PM Subject: Re: RPG integer vs SQL integer. Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> On Mon, Jul 21, 2014 at 3:36 PM, <rob@xxxxxxxxx> wrote:
>Message ID . . . . . . : MCH1210 Severity . . . . . . . : 40
>Message type . . . . . : Escape
>Date sent . . . . . . : 07/21/14 Time sent . . . . . . :
14:57:27
>
>Message . . . . : Receiver value too small to hold result.
>
>In debug mode:
>
>SysAsp=ssts0200.SysAsp;
>SYSASP = 22500008
This is going to sound dumb, but are you sure that's the line that's
producing the error?

John Y.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact