Re: Reasons for using RPGIV

Maybe the new programmer can handle maintenance on all the old code no one
wants to touch. They can stay in RPG/400 and be happy and the rest can
advance.

I do find it amazing that the new person wants to prevent programming in
RPGIV, especially when it is already happening. I understand they may not
be comfortable with RPGIV, and maybe JDE is still completely RPG/400, I
don't know, I've never had to work with it. But it can't help the new guys
job security to say "No we need to do it all the old way."



From:
"sjl" <sjl_abc@xxxxxxxxxxx>
To:
rpg400-l@xxxxxxxxxxxx
Date:
04/15/2011 10:24 AM
Subject:
Re: Reasons for using RPGIV
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx



Dennis -

As I alluded in my original post, this is basically an argument with one
person - a /new/ developer in our shop who once worked for JDE, and who is

of the opinion that there is no need to use anything but RPG/400 to write
code...

On the other hand, there are at least 10 other developers here that
disagree
with her philosophy, and since we already have a substantial amount of
existing RPGIV code mixed in with OPM code in the shop, I don't think she
will be able to muster much support for her position.

In fact, I don't even know why she is pushing so hard when her argument is

clearly untenable.

- sjl


Dennis wrote:
I haven't been following this thread as closely as I might have,
but I don't think the original poster has chimed in about
reasons for this pushback.

Though I am loathe to support such pushback, I have seen
situations where it may seem to make sense. In particular,
a programming farm on the Asian continent does all the
programming work for a particular set of pharmaceutical companies.

These people know RPG/400 to some extent, and ILE not at all.
The company has a position that introoduction of ILE to that
source set introduces a wealth of support issues.

Instantly, the set of individuals who can support a particular change
is reduced until training occurs - and this particular organization
has no desire to retrain. They are able to retain their staff
and keep things interesting by double-teaming their responsibilities.

While Roji may be on the PHP and RPG team,
Koko may be on the Java and RPG team.