RE: DS Group Field Names

My impressions is that in Glenn's case "overchargesLevel1" is not coming from a file, only the other subfields that make up that field are. But if you're in agreement with that, it seems odd that "overchargesLevel1" can be defined by the compiler only if the definition of the other subfields comes from a file vs being explicitly defined. Though I don't really ever see myself using this - I am a -huge- fan of qualified files and reading into data structures (vs a read implicitly loading a data structure).

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Wednesday, March 12, 2014 2:45 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: DS Group Field Names

On 2014-03-11 17:32, Anderson, Kurt wrote:

Hi Glenn,

Only way to get the long names to work (from my test) was to give those long names a definition. I also tried freeform (I know you're on v6.1, but I wasn't sure if you could PTF the freeform back or not), but I'm definitely no pro in fully freeform RPG code yet. I was having issues getting the overChargesLevel1 & 2 lines to autodefine.

Since I don't have the files the fields are based on, I just gave them an arbitrary definition.
dcl-ds overChargesMultiMeter;
overChargesLevel1;
y1vrp1 Length(5) Overlay(overchargesLevel1);
y2vrp1 Length(5) Overlay(overchargesLevel1: *next);

Hi Kurt, you don't have to specify data-type information for free-form subfields if the subfield's definition comes from a file.

dcl-ds overChargesMultiMeter;
overChargesLevel1;
y1vrp1 Overlay(overchargesLevel1);
y2vrp1 Overlay(overchargesLevel1: *next);
...
--
Barbara

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.