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 ..

If you want to ensure a member never gives you that error in SEU the next time you edit it, when you press F3=Exit in SEU, there is an option on that screen to allow you to force it to generate new line sequence numbers for the member again, and specify the starting number and increment.

Also, when you copy a member from one source file to another using CPYSRCF, you also have options to sequence the target member in a similar manner -- for example:
        SRCOPT(*SEQNBR) SRCSEQ(100.00 10.00)

Does that help?

Mark S. Waterbury

On Monday, January 6, 2020, 7:37:00 PM EST, James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:

Ladies and Gentlemen:

This has to be the most uninformative error message I've ever seen, and
given that lately, I've been spending a lot of time writing source
generators, it's one I've seen a lot of.

Is there anything out there that will scan a source member and tell me
*where* the sequence numbers are bad? Eyeballing it takes forever, and
I've never been able to get SEU to tell me anything specific.

And I'd rather not reinvent any wheels.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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