Re: Renaming Fields in the D specs

["Peter Dow" <pcdow@xxxxxxxxx>]

Hi Hans,

I'm sorry, it's probably me, but I still don't get it.  Why isn't the
EXTFLD() keyword enough to distinguish a program-defined subfield from an
externally-described subfield?

SEU does not allow

  d oldPayment    e ds                  extname(PAYMENT)
  d  abc                                extfld(xyz)

it says "Keyword is not allowed for a parameter definition".

Nor does it allow

d oldPayment    e ds                  extname(PAYMENT)
d  abc            s                   extfld(xyz)

it says "LIKE keyword is expected but not found".

To me this implies that I _must_ use the "E" whenever I use EXTFLD(), that I
_cannot_ use EXTFLD() without the "E".  Therefore, using EXTFLD() should
simply imply the "E".  What am I missing?

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax


----- Original Message -----
From: <boldt@ca.ibm.com>
Sent: Wednesday, December 05, 2001 7:41 AM
Subject: Re: Renaming Fields in the D specs


> For the benefit of others, the justification for the design is
> rooted in the need for RPG IV to be functionally compatible
> with RPG III, which allowed program described subfields to be
> added to the end of externally described data structures.  The
> E in position 22 was put there to distinguish the program
> described subfields from externally described subfields.



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com