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

Thanks for all the RDI input.
We use CA 2E 9 (formerly Synon) for 95% our RPGLE coding.
If we decided to review RDI, which version, and how much, I saw several versions.
Several years ago, we had a one site license, version 7.5 or 7.6, only used by one programmer for a special project.
I think it was visual basic related.
The visual basic was converted to something newer, RDI no longer used, and dropped.
Any good RDI links I could review.
Also need a good RDI write-up to send to my manager.

Paul

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

<<One wonders if they still use candles to light their workspaces>> Only if it is 6 characters.

No, as I said in a previous post, I think the opposite. Quit worrying about dragging along the people who have no interest and clean spec RPG.

On Fri, Apr 18, 2014 at 9:47 AM, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:

It's even worse when, with the exception of a few who have been
appointed to management positions, the inmates are on the other side
of the world, but that's a different discussion.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx

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

Then shame on the management for letting the inmates run the asylum.

On 2014-04-18, at 1:45 AM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

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