Re: Ad Hoc key list error

Unless there's a reason to do otherwise (such as changing the key), I
always use the file's key field name(s) in any key field specification
(in both fixed and ad-hoc formats).  This eliminates problems like
this but, more importantly, it documents the acess logic.  It's
another line of code but it's nice having it there; debugging becomes
a lot easier.

-reeve

On 5/2/05, Tony Carolla <carolla@xxxxxxxxx> wrote:
> If you use free form Ad Hoc keylists, i.e.
> 
> chain (field1:field2) format;
> 
> You should be aware, in some cases, if you set up key fields that are not
> the correct size, the program will compile successfully. At runtime, you
> will see an error: "MCH1210: Receiver value too small to hold result."
> 
> Because I have spent the last hour trying to figure out why a record
> wouldn't fit into a DS set up using LIKEREC, and this was really the
> problem, I thought I would share it with the group, and save you some time
> ;-)
> 
> --
> "Enter any 11-digit prime number to continue..."
> "In Hebrew SQL, how do you use right() and left()?..." - Random Thought
> --
> 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.
> 
>