Re: Starting RDi from a green screen

On Tue, 24 Oct 2023 at 04:37, x y <xy6581@xxxxxxxxx> wrote:

Buck, I have development environment commands that run batch processes on
my source (like updating panel groups with refreshed definitions and
content, building internal documentation, and generating SQL template
code). I enhance and fix in a single process so I'm often working with
multiple related members and RDi is *painfully* slow for a one- or two-line
change. My XXM730 command brings the DSPF in SDA, then in SEU, and then
the panel group, and then the RPG, and then the copy books, and then the
binding directory, and then the binding language source, and then the CLLE,
and then the command, and then the command panel group help...and then all
objects are archived before it builds new objects. RDi will be "live
parsing" long after my quick SEU changes are done and the code's compiled.

Ah, I think I understand, but let me propose a use case so that I can
be sure. I have an IBM i-based cross reference tool. When I need to
alter the length of a column in a file, my tooling tells me all of the
places this column is referenced. I can then take that list of PF, LF,
DSPF, PRTF, CLP, and RPGLE source members, direct it into my sequencer
tool, and then one at a time slam through editing each one with SEU ,
pow, pow, pow - all in green screen, all driven by the change cross
reference tooling. Which can also do things like checkout the source,
put it into my dev library, mass compile, and so on.

The batch side is the sequencer, and the editing part of this process
is by your own hand. You don't need the boost of a full fledged IDE;
you're genuinely editing text. I do not think that RDi is a good fit
for this scenario, although it IS possible to turn off the live
parsing/Outline View overhead by command within RDi - that is, you can
have it enabled for the times you want an IDE, and disabled for the
times you just want to type characters quickly.

--buck