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



On Tue, Jun 24, 2025 at 11:12 AM Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

I'm working with a CLLE source member where the line numbers don't start at
1. RDi correctly shows the line numbers, but code4i numbers them starting
at 1. Is there a setting to fix this?

I strongly doubt it. The line numbers in VS Code are automatic and
sequential. The line numbers in IBM i source members are arbitrary,
and not necessarily even integers.

From my point of view, there is nothing to "fix". I think allowing
autonumbering to be off in PDM/SEU, in this day and age, is a mistake
(and a misfeature ever since we stopped using physical punch cards).
To me, *that* is what should be fixed. But I know development for that
is frozen, so it's grandfathered in.

Liam was initially already reluctant to support maintenance of SRCDAT,
and I can totally appreciate that. It would be nice if everyone
abandoned them in favor of Git or similar. But at least the line dates
have *some* meaning, and some people's workflows will genuinely be
disrupted if they are always reset to zero.

SRCSEQ is truly meaningless. There is no sane justification for NOT
always automatically renumbering. If you do a systemwide sweep and
change everyone's SEU option to "always renumber", no one's workflows
will be adversely affected. Most probably won't even notice.

John Y.

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