Hi Jeff, most likely while you were sending this I replied with the
answer. The error was not caused by the IVUL$ or IVLN$ fields but rather
the fields that they were being used to define. As noted the error was
casting suspicion one the wrong fields.
But thanks for responding...
Rob
On 2013-04-02 5:01 PM, Jeff Young wrote:
Rob,
Is the output line for the same file name?
If not, check the field attributes of the output field against the cross
reference for differences.
On Tue, Apr 2, 2013 at 4:32 PM, Robert Rogerson [1]<rogersonra@xxxxxxxxx>wrote:
IVUL$ and IVLN$ are correctly defined on the input spec for INVMASP.
It is on the output that the error occurs. But to me the error does not
make sense. The error is pointing to a line where COST and LANDED are
being defined. And yet the error is saying the IVUL$ and IVLN$ are in
error.
I tried to copy the compile listing to the scratchpad but couldn't.
Feel
free to send me an email off line if you want to see the listing for
yourself.
I'm getting the feeling that the error may be suspect?
Thanks,
Rob
On 2013-04-02 4:05 PM, Mark Murphy/STAR BASE Consulting Inc. wrote:
Or more importantly, check the compile listing to see which lines IVUL$
and IVLN$ are defined in.
Mark Murphy
STAR BASE Consulting, Inc.
[[2]1]mmurphy@xxxxxxxxxxxxxxx
From: "Briggs, Trevor (TBriggs2)" [2][3]<TBriggs2@xxxxxxxxxxx>
To: "RPG programming on the IBM i (AS/400 and iSeries)"
[3][4]<rpg400-l@xxxxxxxxxxxx>
Date: 04/02/2013 03:36 PM
Subject: RE: RNF3316: The item has already been defined ona
Definition,Specification; specification is ignored.
Have you looked at the field cross reference table at the bottom of the
listing to see which source lines the program thinks variables COST and
LANDED are defined on?
Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
[[5]4]TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: [[6]5]rpg400-l-bounces@xxxxxxxxxxxx
[[6][7]mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Tuesday, April 02, 2013 3:22 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: RNF3316: The item has already been defined ona
Definition,Specification; specification is ignored.
Wait a minute. I'm not sure this error makes sense. The error is
000001=OINVMAS
*---------------------------------------------------------------------
* RPG record format . . . . :
INVMAS
* External format . . . . . : INVMAS :
QS36F/INVMASP
*---------------------------------------------------------------------
000002=O IVITM# 6S ZONE
6,0
.
.
.
000020=O IVUL$ 63P PACK 7,2
*RNF3316 30 014100 The item has already been defined on a
Definition
Specification; specification is ignored.
000021=O IVZCOD 64A CHAR 1
.
.
.
000027=O IVLN$ 85P PACK
7,2
*RNF3316 30 014200 The item has already been defined on a
Definition
Specification; specification is
ignored.
000028=O IVDTQT 90S ZONE
5,0
Line 141, 142 reads
014000 C*
014100 C *like define ivul$ cost
014200 C *like define ivln$ landed
014300 C*
So my understanding is that variable cost is being defined like field
ivul$. From the manual "Define a field based on the attributes
(length
and decimal positions) of another field". So ivul$ must be
previously
defined. Does it make sense to be throwing the error?
Rob
On 2013-04-02 2:13 PM, Bob P. Roche wrote:
Has the field that it defined like changed since the last compile? I
think
if it was the same size as the in line code definition the system would
have ignored it. I've seen copied rpg400 code define a variable
multiple
times in line. The definition the same each time.
From:
Robert Rogerson [1][7][8]<rogersonra@xxxxxxxxx>
To:
RPG programming on the IBM i / System i [2][8][9]<rpg400-l@xxxxxxxxxxxx>,
Date:
04/02/2013 01:08 PM
Subject:
RNF3316: The item has already been defined on a
Definition,Specification;
specification is ignored.
Sent by:
[[[10]9]3]rpg400-l-bounces@xxxxxxxxxxxx
Hi All,
Today I attempted to recompile an existing, unmodified program which
has
not been changed in over a year. It failed to compile with an
RNF3316
error on two fields.
The two fields are brought into the program from a file in the
f-specs.
Later in the c-specs the fields are once again dined using *LIKE
DEFINE.
We are on V7R1.
Does anyone know if it was it allowed to define a field twice (once
in
the
f-specs and later in the c-specs using *LIKE DEFINE) in earlier
versions
of the os?
The issue isn't how to fix it but rather how it ever successfully
compiled.
Thanks,
Rob
References
Visible links
1. [10][11]mailto:rogersonra@xxxxxxxxx
2. [11][12]mailto:rpg400-l@xxxxxxxxxxxx
3. [12][13]mailto:rpg400-l-bounces@xxxxxxxxxxxx
References
Visible links
1. [14]mailto:mmurphy@xxxxxxxxxxxxxxx
2. [15]mailto:TBriggs2@xxxxxxxxxxx
3. [16]mailto:rpg400-l@xxxxxxxxxxxx
4. [17]mailto:TBriggs2@xxxxxxxxxxx
5. [18]mailto:rpg400-l-bounces@xxxxxxxxxxxx
6. [19]mailto:rpg400-l-bounces@xxxxxxxxxxxx
7. [20]mailto:rogersonra@xxxxxxxxx
8. [21]mailto:rpg400-l@xxxxxxxxxxxx
9. [22]mail[23]mailto:3]rpg400-l-bounces@xxxxxxxxxxxx
10. [24]mailto:rogersonra@xxxxxxxxx
11. [25]mailto:rpg400-l@xxxxxxxxxxxx
12. [26]mailto:rpg400-l-bounces@xxxxxxxxxxxx
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: [27]RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [28]
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [29]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [30]
http://archive.midrange.com/rpg400-l.
References
Visible links
1. mailto:rogersonra@xxxxxxxxx
2. mailto:1]mmurphy@xxxxxxxxxxxxxxx
3. mailto:TBriggs2@xxxxxxxxxxx
4. mailto:rpg400-l@xxxxxxxxxxxx
5. mailto:4]TBriggs2@xxxxxxxxxxx
6. mailto:5]rpg400-l-bounces@xxxxxxxxxxxx
7. mailto:rpg400-l-bounces@xxxxxxxxxxxx
8. mailto:rogersonra@xxxxxxxxx
9. mailto:rpg400-l@xxxxxxxxxxxx
10. mailto:9]3]rpg400-l-bounces@xxxxxxxxxxxx
11. mailto:rogersonra@xxxxxxxxx
12. mailto:rpg400-l@xxxxxxxxxxxx
13. mailto:rpg400-l-bounces@xxxxxxxxxxxx
14. mailto:mmurphy@xxxxxxxxxxxxxxx
15. mailto:TBriggs2@xxxxxxxxxxx
16. mailto:rpg400-l@xxxxxxxxxxxx
17. mailto:TBriggs2@xxxxxxxxxxx
18. mailto:rpg400-l-bounces@xxxxxxxxxxxx
19. mailto:rpg400-l-bounces@xxxxxxxxxxxx
20. mailto:rogersonra@xxxxxxxxx
21. mailto:rpg400-l@xxxxxxxxxxxx
22. mailto:3
23. mailto:mailto:3]rpg400-l-bounces@xxxxxxxxxxxx
24. mailto:rogersonra@xxxxxxxxx
25. mailto:rpg400-l@xxxxxxxxxxxx
26. mailto:rpg400-l-bounces@xxxxxxxxxxxx
27. mailto:RPG400-L@xxxxxxxxxxxx
28.
http://lists.midrange.com/mailman/listinfo/rpg400-l
29. mailto:RPG400-L-request@xxxxxxxxxxxx
30.
http://archive.midrange.com/rpg400-l
midrange.com
