RE: Field interpreted differentlybetweenphysicalandlogical

Jon,

I'm beginning to question whether this really is a good idea.  Due to
deadlines I coded around the issue by moving the database fields into
the DS fields prior to the call.  The CONST solution sounds like it
might work better.  I'll have to try it when I get the chance.

Rick

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
> Sent: Monday, March 13, 2006 3:56 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: RE: Field interpreted differentlybetweenphysicalandlogical
>
>  >> The DS is externally described and exists solely so that
> I can reference the prototype fields back to the data file.
>
> This seems like a good idea until you encounter the kinds of
> problems you are seeing!  In practice using LIKE on protos is
> probably not a good idea on the whole.
>
> The problem is basically a simple one.
>
> Assume two fields in the file.
>
> F1 is packed, and F2 is zoned.
>
> Define an external DS based on this field and in that DS.F1
> is packed and
> DS.F2 is zoned.
>
> Define the actual file itself on an F-spec however and _both_
> File.F1 and
> File.F2 will be zoned.
>
> So if you say LIKE(DS.F2) in a prototype you just told the
> compiler to define the parm as zoned.  However, try to pass
> File.F2 and you will get a parm mis-match since it is a zoned field.
>
>
> The cure is either to stop doing it and hard code the desired
> parameter characteristics, use CONST on the prototype, or
> always define an external non-qualified DS based on the file
> in the program so that the input field format will match.
>
>
> Jon Paris
> Partner400
>
> www.Partner400.com
> www.RPGWorld.com

Privileged and Confidential.  This e-mail, and any attachments there to, is 
intended only for use by the addressee(s) named herein and may contain 
privileged or confidential information.  If you have received this e-mail in 
error, please notify me immediately by a return e-mail and delete this e-mail.  
You are hereby notified that any dissemination, distribution or copying of this 
e-mail and/or any attachments thereto, is strictly prohibited.