Re: avoid to use the wrong fields

On 8/8/2013 1:15 PM, p.caroti@xxxxxxxx wrote:

...
but with this tecnique, i have the problem that i have to remember to
prefix all my file's fields as, if I use "customer_code" instead of
"S01Ds.customer_code" the program is generated with success, but the
data is not (in this example) displayed in the screen. Is there any
tecnique to avoid this or i'm wrong in something ? do you use this
tecnique ?

I'm not sure whether you want to a) avoid having qualified data structures, or whether you want to b) avoid having the unqualified versions of the names.

a) If you want to avoid having qualified names, and you want to always use CUSTOMER_CODE, then you could just stop defining the data structures, and code the I/O opcodes without the result DS.

write myfile.S01;

b) If you always want to use S01.CUSTOMER_CODE, and you don't want to have the possibility of using CUSTOMER_CODE by accident, then you could add the QUALIFIED keyword to the F spec for the file.

If you code the QUALIFIED keyword on the file, then none of the fields
associated with the file will be defined as standalone fields, and you
will get a compile-time error if you try to use CUSTOMER_CODE.

Since the file is now qualified, you will have to code the record formats as MYFILE.S01, but that is probably a good thing.

D S01Ds Ds LikeRec(myfile.S01:*All) Inz

write myfile.S01 S01Ds;