×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) 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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.