Re: target for a numeric operation is too small on a %lookup?

MQ,

Yup, that was it exactly. Thanks for the reply, but I figured it out
last week and all is well now.

I'm still not sure why it would care - if $edxE1 was a result field, I
could see it - or if it were 5 long instead of 3, but the only place
it's used is as the number of elements to search. It's value would
never be longer than the array length, and wasn't in this particular
case either.

It seems to me that if it really did care, this should be a compile
error rather than a runtime error, as all the info it needs to throw
the error is known before it runs.

Oh well....

Thanks again!

On 6/26/07, MQueue <mqualls@xxxxxxxxxxxxxxx> wrote:

Rick,

My guess is that $edxE1 is defined as 3 long while the array dimension is 4
long. Try defining $edxE1 as 4 long or make it an integer.

HTH,
MQueue



"rick baird" <rick.baird@xxxxxxxxx> wrote in message
news:mailman.12949.1182458290.13580.rpg400-l@xxxxxxxxxxxxxxx
> Hey all,
>
> given the following code:
>
> c if $idxE1 = 0 or
> c %lookup(ERds:ERarray:1:$idxE1) = 0
>
> and the following values:
>
> $IDXE1 = 001.
>
> ERds (data structure)
> ERLICD OF ERDS = ' '
> ERTMCD OF ERDS = 'AMALO'
> ERRYET OF ERDS = 'F'
>
> ERARRAY(1) = ' AGOODF '
> ERARRAY(2) = ' '
> ERARRAY(3) = ' ' (etc. - dim(9999)
>
> which resolves to:
>
> %LOOKUP(' AMALOF':' AGOODF',' ':1:1)
>
> why would I get :
>
> RNQ0103:
> The target for a numeric operation is too small to hold the result?
>
> the result of the %lookup should be zero, and there is no eval.
>
> thanks,
>
> Rick


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.