Re: SEU %scanRpl produces RNF0604 error when prompting, but compiles without error

Paul you are doubly wrong! (I tried for 3 to strike you out but..)

First you can't really share air-nailers all that well. If a guy is attaching the top plate of a wall at one end of the studs he needs one and another guy is putting the bottom plate on the other end it doesn't work very well to share. You might as well have one guy doing both ends. Plus then there is the variety of the things, roofing nails, framing nails, finish nails etc.

Second you CAN share RDi! They have had an option for quite a while now to license to the server. WHen you connect if a license is available you get it and use it. So you can load the software at home, on your laptop, on your work desktop etc and use it everywhere or you can purchase 5 licenses shared across say 8 developers. It mostly depends on how much time each needs to be in the tool.

OK Weak three, you can use RDi for Cobol AND RPG. :-)

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 4/18/2014 2:25 PM, Paul Fenstermacher wrote:

But Larry, if the builder has 1 carpenter he only has to buy 1 air-nailer and if necessary it can be shared with other carpenters. Companies that have 500 developers find it more difficult to purchase 500 RDi licenses and they can't be shared.

Paul Fenstermacher | Sys Admin, Sr | Corporate Systems - POWER Systems
Administration | Jack Henry & Associates, Inc.
663 West Highway 60 | Monett, MO 65708 | 417-235-4114 x177389 |
pfenstermacher@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Thursday, April 17, 2014 11:30 PM
To: Midrange Systems Technical Discussion
Subject: Re: SEU %scanRpl produces RNF0604 error when prompting, but compiles without error

IBM Decided to spend their money on one tool that has vastly more capability and more opportunity for enhancement. It's also based on tools used for other languages so it's familiar to many many more developers than SEU.

Were IBM to continue to maintain both tools there would be either fewer features in RDi or both it and SEU would be more expensive.

And there is no force. You can continue to utilize SEU for your editing you will simply find that you are becoming less and less efficient while with RDi you become more and more efficient.

IBM Quit manufacturing AS/400s and then iSeries and then System i. They didn't do so to force you to buy a Power System they did so because Power Systems are far superior in capability and performance. You can still run an AS/400 (and some DO!) but you'll spend much more money for the same performance.

As to the cost, that argument doesn't hold water for me. It's like a builder who refuses to purchase an air-nailer for his carpenter because it's expensive and the hammer he already owns still works.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 4/18/2014 12:00 AM, Alan Campin wrote:

No, IBM decided to force people to buy RDi by stopping to update SEU
with new releases. I am using at work great but you have to buy and a
lot companies won't buy.
On Apr 17, 2014 9:49 PM, "John Yeung" <gallium.arsenide@xxxxxxxxx> wrote:

On Thu, Apr 17, 2014 at 11:16 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

There was a time when IBM created FSEDIT. It was warmly welcomed
because it was such an improvement over the SEU of the time.

Now we get awesome tools like RDi and we bash them? I don't get it.

I don't see anyone actually bashing RDi, so I guess you mean folks
are bashing IBM. Well, perhaps the situation is different now, but I
don't know. Was FSEDIT expensive and SEU out of date with respect to
the compiler?

John

On 4/17/2014 10:49 PM, Alan Campin wrote:

SEU frozen at v6r1. Anything above that level will not work. Stinks
big time. Have to get RDI if you want syntax checking.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.