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

Most companies I have worked didn't want to pay for programmer education and
new tools.
Probably because they were running lean and IT management didn't want to
spend the time fighting the bean counters with justifications.


Norm Dennis

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Friday, 18 April 2014 1:46 PM
To: Midrange Systems Technical Discussion
Subject: Re: SEU %scanRpl produces RNF0604 error when prompting, but
compiles without error

Most places it isnt the companies. Its the programmers who refuse to
change. They yell so loud that the company says only rpg 3 coding allowed.
On Apr 17, 2014 11:28 PM, "DrFranken" <midrange@xxxxxxxxxxxx> wrote:

Then SEU will continue to work for you. If you are maintaining old
code then an old editor will work as it always has.

The question is why do so many companies hold back their developers?
What value is there in keeping people from using better tools to
become more efficient and write better code?

- Larry "DrFranken" Bolhuis

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

On 4/18/2014 1:13 AM, Alan Campin wrote:

In practical fact it means nothing. The people at my work are still
using data structures to convert dates, moves, six character
variables and

fixed

format to write new code. What does the whole thing mean to them,
practically nothing because they are still writing RPG III and don't
even use the built-in functions and that is going to be true in most
iSeries shops including my previous company and previous company and
previous company over the last 20 years since ILE and RPG IV was

released.

On Thu, Apr 17, 2014 at 10:30 PM, DrFranken <midrange@xxxxxxxxxxxx>

wrote:

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.

--
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.



-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4569 / Virus Database: 3882/7360 - Release Date: 04/17/14
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4569 / Virus Database: 3882/7360 - Release Date: 04/17/14