Re: Why keep "old" code (Was RPG III)

Yes, I understand, but I still agree with the argument of - every time you 
touch a new source member - just convert it to RPG IV.  I mean that takes 
- no time at all.  Do that at-least.  Then maybe also convert to /Free - 
but that's not as  important as converting at lease to RPG IV.


Jeff Stevens
Mize, Houser & Co. P.A.
913 451 1882
JStevens@xxxxxxxxxxxxxx





"Monahan, Kevin" <KMonahan@xxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
02/09/2007 08:14 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"'rpg400-l@xxxxxxxxxxxx'" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Why keep "old" code (Was RPG III)






Mostly playing devil's advocate here.....
Many packages out there (we happen to use JDA, which is a mix of RPG III 
and
RPG IV) were written a few years ago and never updated by the supplier. We
have made modifications to their base code, in some cases pretty
extensively. 
Now some might say, chuck the software and buy something from a company 
that
is keeping up with the times.  If you have a few spare millions of dollars
around, that's great, but otherwise its not feasible. 

Yes, we could make these mods in RPG IV or /Free, but we haven't taken the
time (poor excuse # 1).  Some of us write in RPG IV, some even use /Free,
and some of us are getting our arms around SQLRPG, but with most of our
projects being "reactive" and need to be done/fixed/implemented yesterday,
we do the job in the quickest way possible. 

It's a slow change to get to the newer stuff, and the business expense to
re-write stuff just to bring it up to a modern method of doing something
that already works, just isn't justifiable. 

That being said, we (the programmers, or at least some of us) are slowly
pushing the envelope.  We are soon to start a project to get us off 9600
baud modem connection to some external partners and move to SFTP!  We're
moving into the '90's!  As for the argument that we should leave and go 
find
a shop that does the new stuff, that is also not easy, at least not in the
Boston area, and I for one have no desire to leave New England. 

I'm sure I'll get some heat for this, but there are some instances where 
"if
it ain't broke don't fix it" does have some (small) merit. 


Thanks, 

Kevin Monahan 
Sr Programmer/Analyst 
Casual Male Retail Group 
781-828-9300  x2785 


-----Original Message-----
From: rpg400-l-request@xxxxxxxxxxxx [mailto:rpg400-l-request@xxxxxxxxxxxx] 

 
That's what I especially like about being a one-man shop: There was 
absolutely no argument, discussion, politics, or whatever about ditching 
the RPG III programs (converting to IV) and writing all new stuff in 
IV.  The excuses that I hear for not programming in IV are as lame as 
excuses get.


I "attended" a webcast yesterday by Susan Gantner on /free format.  One 
of Susan's arguments for using /free was that it looks more like 
"modern" languages like Java and C, which the few kids coming out of 
college IT courses are used to.  Besides not being able to code /free 
III code, a similar argument applies here: Managers are holding back 
(deliberately?) their programming staff and, just as bad, harming their 
companies because they can't/don't take advantage of better methods and 
available technology. 


But I try to keep an open mind.  I'd certainly be willing to hear of any 
reasonable excuse for sticking with III.  And "It's company policy or 
mandate" doesn't cut it.


                 * Jerry C. Adams