|
"Charlie Ramsdale" <Charlie_Ramsdale@xxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx
06/22/2007 03:06 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc
Subject
Re: [WDSCI-L] Basic RSE Editing questions
Well, Golly. That was quite a bombardment of helpful answers to Tim's
questions - many of which I didn't know myself. I was faced with saving
several emails or tediously summarizing everything into one email....
Being a slow Friday, I chose the latter. :o) Here's my compilation if
anyone else is interested in saving just one email with several helpful
hints.
***************************************
Hello to all,
There has been lots of talk about this product that has spilled over
onto the midrange list, and it has me once again attempting to give it a
shot. I hate to think of myself as non adaptive and unable to embrace
new technologies, methods, etc. So hear goes again. Currently I'm only
coding old school RPG type programs, so the following questions pertain
to RSE.
And most of the following relates back to how I do things in PDM/SEU,
only because that's all I know at the moment. I attempted a fairly easy
modification to an existing program, and came up with the follow list of
things I found that I take for granted in SEU.
1. Is there a way to list libs, objects, members, etc in the Remote
Systems view with descriptions?
Violaine Batthish: The tree view doesn't support this - although if you
look at the properties view - you will see the description when an item
is selected in the tree view. You should probably try the table view.
2. Can I condition page ups and downs by cursor position? Or at least
jump the cursor to the top or bottom of the displayed view, then I could
roll by line up or down. Violaine Batthish: Keys can be easily remapped to do other things -
check the mailing list archives for discussions on this at length.
You'll also want to read the reference help for what LPEX actions are
available/do (scrollTop, scrollUp come to mind)
Jim Essinger: Try this from the archives; http://archive.midrange.com/wdsci-l/200612/msg00013.html
How to set an Alt + xx key to position the current line to the top or
bottom of your source window. I use the alt page up and down keys, I
also have alt + t set to put the current line at the top of the editor
window.
Sam Lennon: Ctrl-t (v7) will put the line where the cursor is at the top
of the screen.
3. In SEU, when I hit <enter>, I know it has been saved, even if I
loose my session. Do I have to continually save my work? Violaine Batthish: Remote Systems LPEX Editor has an auto-save feature.
Default is set to every 5 minutes. Check out Windows>Preferences,
Remote Systems>Remote Systems LPEX Editor
4. In SEU, when I hit enter, the editor will automatically position my
cursor to where I need to key additional data? I know tab moves me to
the next input position, but not whether it requires input. And by the
time auto syntax checking informs me, I have spent time reading the
message, relocating my cursor, etc. Violaine Batthish: There is no way to currently do this. It is on our
list of requirements.
Adam Glauser: Automatic cursor positioning can be configured by choosing
'Preferences' from the 'Window' menu. In version 7, you are looking for
'Remote Systems -> Remote Systems LPEX Editor -> iSeries Parsers -> ILE
RPG'.
5. Do I have to use the mouse to copy lines from one member to another?
Violaine Batthish: Standard windows copy/paste keys can be used, along
with a few extras provided in LPEX (check the Edit menu for selection
options)
Adam Glauser: To copy X lines, put your cursor is on the first line of
the block you want to move, press Home, then hold Shift and press the
down arrow X times. Now press Ctrl+C, then Shift+F6 (this is like
Alt-Tab in windows, but for LPEX editor tabs) until you get to the
target member. Now find the line you want to insert at, and press
Ctrl+V.
Dave Shaw: Another method not mentioned yet is to mark the lines to copy
using Alt-L, and then copy them into position using Alt-C. The lines
will be inserted beginning with the line after your cursor position.
You should also explore the other Select/Selected functions, which are
listed under the Edit menu with their keyboard shortcuts.
6. How can I copy field names in to the member? I added a table to the
Table View, I can see all my fields, but can't copy and paste from
there. Violaine Batthish: Drag and drop from table view to RS LPEX is currently
not available. It is also on our list of requirements.
7. After compiling, getting errors, and fixing them, and recompiling
successfully, the error messages are still showing in the edit view.
How can I get rid of them with out closing the member?
Violaine Batthish: Ctrl+F5, or either Source>Remove Errors, or
Source>Refresh. Its on our list of requirements to automatically remove
these during error list reloads.
Adam Glauser: Click the X icon in the top left part of the iSeries Error
List view.
Steven Morrison: Remove messages from the source by choosing
SOURCE/Remove Messages from the top of the screen. While you have the
Error List window open, click on the triangle in the top right corner of
the window, choose Show Severity and uncheck Information to not show
informational messages. From the same menu, click Messages, choose
Insert Selected Only. This will only insert the message you click on
from the Error List Window into the source, and will remove the previous
error message when you choose another from the Error List Window.
8. The outline view of the RPG (or other) program doesn't have any way
to show the TEXT associated with the field in a file. Showing the
properties of fields in files would be very nice.
Rick Chevalier: Right click on a physical file object (not sure if it
works on logical files yet) in RSE tree view and select show in table ->
fields. This will open the iSeries Field Table View which gives all the
field information.
Violaine Batthish: Try right-clicking on the line with the F-spec and
select the Show fields menu option.
Mike Driscoll: If you are using 7.0, you are also able to bring up a
Field Table View by highlighting any (PF, LF, DSPF, etc...) file in an
RPG program's F-Specs then select Source->Show Fields from the Menu Bar.
9. Where can I find a list of enhancements in V7?
Violaine Batthish: You can find the list here:
http://www-306.ibm.com/software/awdtools/wdt400/news/ga700.html
Believe it or not, I had a lot more questions, but figured many of them
out.
Which brings up my last question (for now:). How do you work through
learning the functionality of this application? Currently I'm just
stumbling through the basics, and I know I'm not doing many things the
most productive way. Violaine Batthish: I recommend that you try the tutorials included in
the product as well as the PDM/SEU transition to RSE/LPEX - which was
revamped and rewritten for v7.0. Also, if you go to the WDSC web site
(http://www.ibm.com/software/awdtools/wdt400) and search the support
section - you will find additional tutorials and the labs from COMMON.
Adam Glauser: Don Nitke has a site with a bunch of tutorials. I don't
have the link, but if you search the archives it has been mentioned a
bunch of times (http://archive.midrange.com/wdsci-l).
Joe Pluta: You can use the help and tutorials from within the product
itself. There are some free tutorials out on the web, including my own
first one. You can buy my book, WDSC: Step by Step, which is based on
version 5.1.2, but still pretty valid. You can buy my training course
from Rochester Initiative which is now available for version 7. You can
go to a jumpstart at a technical conference, or an all-day standalone
seminar sponsored by your local user group. Or you can contract with
someone to come onsite and provide training.
Thanks for all you help, Tim
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.