RE: Problem with non QUALIFIED DS

Actually it would have if the data structure was defined in one copybook and copied into the copybooks that needed it. It would have been defined only once, in the first copybook brought into the module, all others would have hit the /Eof directive.

There are two caveats, you can only <tic> have 32 levels of /copy and/or /include statements, the other is that the SQL pre-compiler will only go one level deep (IIRC) but the pre-compiler doesn't like using templated data structures anyway, so that should not be a problem.

Duane Christen


--


Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx

Visit PAETEC.COM


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, September 23, 2009 2:41 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Problem with non QUALIFIED DS

In the OPs case though Duane this wouldn't have helped. he wasn't copying the entire prototype file twice - he had a DS that was duplicated inside multiple different prototype files. That's why I had the conditionals embedded in the copy member.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On 23-Sep-09, at 2:41 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

I disagree with Jon, I use only one set of compiler directives, if the
copybook name is "RCS0000" and thus the name of the service program is
RCS0000 in my environment, the compiler directives would look like:

--
This is the RPG programming on the IBM i / System i (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.