|
Buck Calabro wrote > The very top things that I would love to see in SEU: > 1) Ability to edit multiple members simultaneously > 2) Ability to write macro commands > 3) Ability to "undo" editing mistakes I am still doing my programming on SEU inside PDM on green screen ... which V4R# will this no longer be an option & what alternative editors will I need to learn? With respect to "multiple members" edited simulaneously. A lot of the code changes I have worked with recently involve an RPG program that interacts with a DDS defined screen or report & I am on a multi-session work station. It is a simple matter to have one session in the source code of the DDS screen & another session in the source code of the RPG program, so that as I make decisions how to do stuff, I am tweaking the code in both areas in concert, then when I am done ... -1- end the DDS session & 14-compile & -2- when/if that compile is successful then 14-compile the RPG session so it includes the new DDS object. With respect to "undo" mistakes. In my reality, if I make a keying error in SEU, F5 undeletes changes on the current screen. For example, I accidentally touch the field exit key and wipe out one or more lines of code. F5 brings them back. If I have previously enter keyed the oops & it is a program previously saved or that I am modifying, I can F15 get at earlier version of the code, or if do not want to save this mess, I can always F3 out of this & say No to saving my work, then there is the option of getting to another session & copying the last save elsewhere so that I can save where I am anyway & also have the earlier version. We learned working with PCs that when word processing is good idea to periodically save our work because the platfom was unstable ... editing software on AS/400 what is unstable is ME ... ie I am much more likely to do a typo than for anything else to go wrong. However, I am not worried about the typos I catch with OOPS I just noticed that my keying was disconnected from my brain ... what I need a better job of catching is the "typos in my brain" where there is some flaw in my logic that goes unnoticed until testing or worse, gets into production. Mark. Lazarus wrote: > >What features would you like to see them include as enhancements in SEU? > > There is plenty. A very short list: > > Split / join lines. > Dual editing sessions, not just browse on the 2nd session. > Expansion of /COPY members. > Copy / Move of multiple blocks (or non-contiguous individual lines) to one > target location. > Bookmarks. > Copy / Move Replace line (as opposed to overlay). > > The list goes on... > > -mark Copy / Move ... I use CC on first & last lines of a block to be copied or MM to move then A on line to insert this after or B to insert this before ... what is it you are asking for that this not do? Bookmarks ,,, I think we would need some dictionary of places that have pointers. I have been using F & name of subroutine & 18 to get to beginning of that subroutine & other variations - but the technique I need to learn is ... when I have a copy of the compiled program in front of me ... how do I jump to a particular LINE # ? Al Macintyre ©¿© MIS Manager Programmer & Computer Janitor of BPCS 405 CD Rel-02 running on AS/400 V4R3 http://www.cen-elec.com Central Industries of Indiana--->Quality manufacturer of wire harnesses and electrical sub-assemblies +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.