RE: Long subfield name definition

[Dan Bale <dan.bale@xxxxxxxxxxxxxxxxxxxxx>]

Honestly, this smells like a bug.  Barbara may differ, but it seems to me the compiler should be able to handle this.

Of course, one workaround is to use the short name from the file.

If you're using long names, that's probably the best reason to ditch the fixed format specs.

- Dan

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Vern Hamberg via RPG400-L
Sent: Sunday, August 4, 2024 6:29 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Cc: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Subject: Re: Long subfield name definition

A couple problems here -

1. DS is 1 character off, to the right - of course, that doesn't affect the long name, just that it showed up in RDi as incorrect 2. The first part of a continued name has to be within positions 7-21, as I just read in the docs - so the following will work -

D myDS            DS
D   SField1
D  Sfield_long_n...
Dame

or, to be a little "prettier", since the first part doesn't have to fill position 7-21, and it doesn't have to start at position 7 -

D myDS            DS
D   SField1
D  Sfield_long...
D        _name

If you did have the from/to or length specified, they have to be after the last part of the name

This is all so much cleaner (better?) in free-form, IMHO -

dcl-ds myDS;
   SField1;
   Sfield_long_name;
end-ds;

Regards
Vern

On 8/4/2024 2:21 AM, Dave wrote:
> Folks,
>
> How do I code the long subfield name shown below in myDS?
>
> D myDS             DS
> D   SField1
> D  Sfield_long_name...
> D
>
> Each field is already known to the program as they are fields of an
> externally described file, hence no definition is given.
*** CONFIDENTIALITY NOTICE: The information contained in this communication may be confidential, and is intended only for the use of the recipients named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. ***