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

Thanks Barbara,

The length of the index was too small, and I fixed it that way, but I
was sure this was not an error that should have made any difference -
or one that should have been caught at compile time rather than run
time.

It's good to know it was a mistake rather than 'working as designed'.
Even I make mistakes!

;-)

On 6/29/07, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

rick baird wrote:
>
> given the following code:
>
> c if $idxE1 = 0 or
> c %lookup(ERds:ERarray:1:$idxE1) = 0
>
> why would I get :
>
> RNQ0103:
> The target for a numeric operation is too small to hold the result?
>

Rick, this sounds like APAR SE28850. There will be a PTF available soon
for v5r3 and v5r4.

The circumvention is to define the length operand ($idxE1) as an
integer, or to make it an integer for %LOOKUP by using %INT:

%lookup(ERds:ERarray:1:%int($idxE1)) = 0

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