×
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.
You need to know which are dupes and then locate those...
Try this in SQL...
create alias qtemp/mySrc for <library>/<source file>(<member>)
select distinct(SRCSEQ), count(*) from mySrc group by SRCSEQ having count(*) > 1
// Using those source sequences...
select rrn(mySrc) from mySrc where SRCSEQ = <numbers from above>
drop alias mySrc
Roger Harman
COMMON Certified Application Developer – ILE RPG on IBM i on Power
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, January 06, 2020 4:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: EDT0304: Duplicate or non-ascending sequence number.
On 1/6/20 4:50 PM, Mark Waterbury wrote:
James,
I don't think it is a true "error" message, but rather, just a warning message, telling you that this member has been "re-sequenced" by SEU ..
. . .
Does that help?
Not really; if it's showing up on generated source, then the source
generator is flawed, and needs to be corrected. But if I don't know
where the bad sequence number is, then I don't know where to put the
correction.
--
JHHL
midrange.com
