Re: Why upgrade from WDSC to RDi?

Nicola,

Sorry, but I believe the demo version is the real product. There is
simply a license associated with it. I'm on version 7.0 and it's been a
while so I don't remember--do you use Installation Manager (IM) on version
6? If so you can select the "Manage Licenses" icon on the top of the
icons to the right of Installation Manager. When you do, you'll see a
'License Type' column. This displays the license to any installed
packages. For WDSC 7.0 I have a permanent license. However, my RDi demo
had a trial license. You can actually install the permanent license on
top of trial software installation and make it a permanent install.

That said, I would have to disagree that the SEU commands are quicker. I
would say you are simply more used to them. If you fully go with the LPEX
keystrokes, you'll find they offer some advantages. The caveat is you'll
have to take the time to retrain yourself. To copy a line use Alt+L and
it is marked--it doesn't matter what column you're in. Then move to the
line above where you want the new line and you can use the Alt+M or Alt+C
and the line is moved or copied respectively--again it doesn't matter to
what column the cursor is positioned. You can even start marking a block
of lines by pressing Alt+L, holding the shift key and using the up and
down arrow keys to add to the blocked area. Using the old SEU commands
requires moving to the prefix area, using the cut and paste (c&p) logic
(old-school--Ctrl+Shift+insert--or new--Ctrl+C), you have to be in column
one. That takes extra effort that I've found takes away from my
productivity.

For the overlay SEU command you can use the Alt+Z keystroke. That one
really takes a while to get figured out. You block the area you want to
copy (using any blocking commands (I prefer to block a rectangle using
Alt+R for the top left and Alt+R to mark the bottom right.) Then move to
where you what to overlay the marked text and press Alt+Z. It's
definitely different that SEU's C and O commands, but I'm starting to
really enjoy using it.

Again remember I said it takes the time to retrain yourself, but the LPEX
keystrokes can be very productive. When I learned the editor, i
figuratively tied my SEU and c&p hands behind my back. I forced myself to
exclusively use LPEX and it's keystrokes. I can't and wouldn't go back
now.

By the way, I too would be considered a dinosaur. I program in COBOL (in
addition to RPG) and I still use and love my 35mm film camera--habbits of
over 30 years can be hard to break.

Regards,
Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 05/12/2009 01:00:05 PM:

----- Message from nb@xxxxxxxxxxxxx on Tue, 12 May 2009 14:23:37 +0200

-----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

Re: [WDSCI-L] Why upgrade from WDSC to RDi?

This is probably not what you were wanting to hear, but

Paul, first of all, thanks for the link, i find it very useful as i

found

shortcut that i was really missing.

As for LPEX editor, i'm already using WDSC .6x, so found it quite nice.
However, up to WDSC, SEU-Like function was working pretty well. I know i
can replace them with shortcut, but still i find that in certain case,

old

SEU sintax is faster. In fact, i'm using a mix of both LPEX and SEU

sintax

with no problem. I already dropped SEU for development.

For example, it is much faster to do M -> A on a single row (or mm+mm ->

a

to a block row) than select the row list (taking care you're il LPEX

col1)

do CTRL+INS (old c&p school, you know) move down 'n' row, be sure *to be

in

col 1* and do SHIFT+INS. As a matter of fact, i didnt' fund actually, a
good replacemento for C -> OO + OO, which i use a lot.

Worse, since i'm used to to it mindless, i found myself lose piceces of
source. If SEU-like had been removed, i would have rant something, and

move

on, but in this case, it silently *delete*row* without moving.

And, since we're considering to move from a free WDSC client to a costly
RDi, i want to check before if this is a RDi Time-bombed bug, or it's
generally.

If (or when) i wil have the payed version of RDi, i can report (if
present...) the prob to IBM and hope for a fix. But actually my prob is
more to go to CEO, ask for money for a product we got for free until ...
ehr... today, and get a buggy one. Small, with workaround, but buggy. My
CEO won't like this....

I dont' think the prob pertain to WDSC: previous instance was working

well.

I'm back to WDSC 6.0 and it work nice. I have understand that RDi 7.5.0

is

a newly written product that is ismilar to WDSC but completely

rewiritten.

I use the "seu" line commands all the time and haven't had a problem.

I'm using RDI-SOA 7.5.0
Thanks. so i have to think this problem will happen only onto the demo.

--

Nicola Brion
Tech Fossil (Often called a Dinosaur) - ancient animal that make things

to

work.

"La disumanita' del computer sta nel fatto che, una volta programmato e
messo in funzione, si comporta in maniera perfettamente onesta"


--
This is the Websphere Development Studio Client for iSeries (WDSCI-
L) digest list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.