Re: How to define long field names

["Joe Teff" <jteff19@xxxxxxx>]

>Joe, I'm sorry I took so long to answer...  We're in the midst of moving
>and my email is a shambles.
>
>Yes, you can use long field names on any of the "extended factor 2"
>specification lines (IF, EVAL, DOW, etc. but NOT on traditional factor 2
>lines (MOVE, Z-ADD, etc.)
>
>DThisIsAReallyLongStupidNameThatExtendsBeyond...
>DTheColumnBoundaries...
>D                 s              1a
>
>C                   Eval      ThisIsAReallyLongStupidName...
>C                             ThatExtendsBeyond...
>C                             TheColumnBoundaries = 'Y'

Thanks for responding. I did figure this out. My problem wasn't using
it in my C-specs, but rather the definition in the D-specs. I tried to
define is as
   D RestrictedI...          C                  1999999
   D temClass
 because I assumed that the extended line would follow the definition
line. Once I changed it to
   D RestrictedItemClass...
   D                          C                   1999999
it worked fine. Too bad the manual didn't show an example as I thought
I was dioing exactly what it said. Maybe I just didn't find the right
manual!

Joe Teff

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *