×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
COST on lines 3006600 and 014100 and LANDED on lines 3006700 and 014200.
\
Maybe this is what the compiler is trying (albeit obliquely) to point
out.
Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Tuesday, April 02, 2013 4:36 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: RNF3316: The item has already been definedona
Definition,Specification; specification is ignored.
They are look to be defined correctly as expected.
But the way I read the error it is saying that IVUL$ and IVLN$ are
being
defined at line 14100 and 14200
On 2013-04-02 3:35 PM, Briggs, Trevor (TBriggs2) wrote:
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
[1]TBriggs2@xxxxxxxxxxx
-----Original Message-----
From: [2]rpg400-l-bounces@xxxxxxxxxxxx
[[3]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][4]<rogersonra@xxxxxxxxx>
To:
RPG programming on the IBM i / System i [2][5]<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:
[[6]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.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
