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



RDi goes to the line number.

There is a preference that should be activated to correct the sequence in the source.
"Resequencing lines at save" (preferences Remote Systems/Remote Systems LPEX Editor)

If you always have this checked "Resequencing lines at save" then you won't have any issue locating the line number.


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Javier
Sanchez
Sent: Friday, April 16, 2021 8:00 AM
To: wdsci-l@xxxxxxxxxxxxxxxxxx
Subject: [WDSCI-L] RDi - Source line like in PDM should work the same

It turns out so weird that RDi doesn't do what in green screen you do when
typing on the line number at the left any line number that is approximate
to the one you want to get in your source.

Line numbers in RDi of course don't coincide with the source sequence, but
to me it should do the same. Suppose I wanted to get to source line
0310.00 in my source, if I type 310 at the left area where the code line
is, RDi should react and take you there just like if you were doing a SETLL
in an RPG program. Doing so in RDi, well, it lets you type in that but it
doesn't react.

Going to a line number is not the same.

Or am I doing it wrong?

Thanks.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.