RE: [Easy400Group] Re: ILE RPG or RPG/400

[Chet]

First off you should only change when the business model changes (the client decides that they need to have a web presence or some new application dictates the requirement for an upgrade).  I had a client that was happily chugging along on System/34’s (yes I am that old) until the day came that they were going to be implementing EDI with there largest customer.  They didn’t want to “rig” something together with a pc so they bit the bullet and moved their applications to a F35 using S/36 EE.  A business could go broke trying to stay on the bleeding edge of technology.  This is what is fueling the open source movement, why discard good pc’s because gates came out with vista when you can run open source linux and extend the life of the hardware.   From: Easy400Group@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jon Paris Sent: Friday, February 17, 2006 5:42 PM To: Easy400Group@yahoogroups.com Subject: RE: [Easy400Group] Re: ILE RPG or RPG/400   >> I have clients that are hanging onto RPG II and OCL tooth and nail. It >> meets their current business needs so who am I to tell them otherwise. >> There are more out there than most realize which is why all of us will >> always have plenty of work. First of all I should say that I have some sympathy for RPG II users - conversion is much harder for them than for RPG III users who have no excuse. On the other hand - and I'm not trying to be rude.  This is really addressed to all those who find themselves in your position. The answer your question "who am I ..." is that _you_ are the professional who should be able to demonstrate to them some of the problems/risks that they face if they stay in this environment.  And of course the benefits to them of moving forward.  One of these risks as I noted earlier is the just announced end of IBM support.  As of V5R5 (or whatever it is called) RPG/36 becomes a PRPQ not a product.  Assumedly the S/36EE will follow at some time.  Maybe your customer is OK with it but I don't want to have my business rely on unsupported software. Think of the old code as a Model T (the vintage is similar <grin>) - lovely to own one, great for a gentle drive in the country on a Sunday.  But would you want to rely on it if you had emergency medical supplies to deliver? The other issue of course is that it only takes one person in the upper management chain to change (takeover, death, senior family member standing aside, etc.) and all of a sudden "meets our current business needs" becomes "why are we using this old crap".  Do you think that in those circumstances they will look to you to lead the modernization effort?  You are much more likely to become the scapegoat as all those who gladly let things drift along try to get on the right side of the new boss by pointing out how unresponsive you were to their needs etc. Jon Paris SPONSORED LINKS How to format a computer hard drive Cobol programmer Iseries 400 How to format a computer YAHOO! GROUPS LINKS  Visit your group "Easy400Group" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.