Re: RNF3316: The item has already been defined on a Definition,Specification; specification is ignored.

Yes, that would have nipped the problem in the bud...
On 2013-04-03 12:11 PM, DeLong, Eric wrote:

That's one reason I LOVE qualified data structures for copy members...

-Eric DeLong

-----Original Message-----
From: [1]rpg400-l-bounces@xxxxxxxxxxxx [[2]mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Wednesday, April 03, 2013 11:04 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: RNF3316: The item has already been defined on a Definition,Specification; specification is ignored.

For the archives.

In my case the program originally defined COST and LANDED in the c-specs
using *LIKE DEFINE. Later, a module from a service program was copied
into the program. As part of the copy a data structure was also
included. Subfields of the data structure had the names COST and LANDED.

So at compile time the fields COST and LANDED from the data structure
would be defined first (as they were d-specs) and then the program
attempted to define COST and LANDED a second time in the c-specs.

Thanks to all,

Rob

On 2013-04-02 6:08 PM, Jon Paris wrote:

On Tue, 02 Apr 2013, at 16:52:30, Robert Rogerson [1][3]<rogersonra@xxxxxxxxx> wrote:


Ok, I went ahead and commented out the two *LIKE define lines. I expected
that this would result in variable COST and LANDED being undefined. But
it was not the case.
From the listing I found that both COST and LANDED were defined in a new
module added to a called service program.

Just so we get the archives straight ... there is no way that COST and LANDED would be defined by calling a Service Program routine. Perhaps it was because they were defined in the prototype source for the procedure or ... ????

Please confirm exactly how they were defined because the compiler has zero visibility into the content of a Service Program - in fact it doesn't even attempt to access it. That is a run-time process.


Jon Paris

[2]www.partner400.com
[3]www.SystemiDeveloper.com

References

Visible links
1. [4]mailto:rogersonra@xxxxxxxxx
2. [5]http://www.partner400.com/
3. [6]http://www.systemideveloper.com/

References

Visible links
1. mailto:rpg400-l-bounces@xxxxxxxxxxxx
2. mailto:rpg400-l-bounces@xxxxxxxxxxxx
3. mailto:rogersonra@xxxxxxxxx
4. mailto:rogersonra@xxxxxxxxx
5. http://www.partner400.com/
6. http://www.systemideveloper.com/