× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Standards and Egos (was RE: ILE Propaganda)
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Tue, 26 Jun 2001 09:11:53 -0700
  • Organization: Pacer International

I agree we need standards, and agree it would be very nice to be able
to go back through all the old code and bring them up to standard, and
realize that this is just not feasible in 99% of the cases.  But a lot
of times what you wind up with can be a mess.

You have standards in RPG II, and you use them.  You switch to RPG III,
come up with new standards, and use them in new programs.  Then you switch
to RPG IV, new standards, then you implement RPG IV an come up with new
standards, then you start using new op codes and implement those standards.

What do you wind up with?  A bunch of programs all with their own standards.
A lot of the stuff converted from S36 RPG (RPG II) in applications I've seen
(admittedly, all from the same vendor) were basically converted and as 
little code touched as possible, so you wind up with an RPG II program that
compiles and runs in RPG III.

Now the decision has to be made.  You are now on RPG IV with ILE using all
these neat new %BIFs such as %Error and service programs and... you have to
go back and revisit one of these ancient now RPG III programs that were
coded in RPG II.  It will take you 10 minutes to put in the program fix
that some want's, if you stick to the program logic and standards in that
program, or you can spend the next 2 days or more converting it to RPG IV
with all the new bifs, you are basically rewriting the program.

Is it then feasible to do this?  Is the cost incurred justified from an
accounting point of view?

I'm not sure, this is a question, not a statement.  I've done it both ways
when I've come across these, I've spent the 10 minutes to make it work, and
I've spent the 2 days converting it (converting from internal to external
declarations, etc...).

Perhaps there is justification in bringing up all existing programs to new
standards when they arise, then you won't fall into this trap.  But, it is
a lot easier to convert a properly written RPG III program to RPG IV and then
implementing RPG.  It is not that easy to go from II to IV.

I thought I was out of this RPG II hole since the application we were using
from S36 days from a vendor we are abandoning (we are already migrating off).
But, management purchased another application from them.  RPG III.  Right?
Of course not, RPG II converted to RPG III to compile and run. Argh!  I hate
that company's products!

Regards,

Jim Langston

Me transmitte sursum, Caledoni!

SCarter@rsrcorp.com wrote:
> 
> I think what we are talking about here is that if your shop does not yet
> have standards now is the time to set them up....
> I don't think anyone expects a company to rewrite all of their programs to
> a new standard.  But do start using standards on all NEW
> Projects so that going forward any NEW application has been coded to the
> organization's standards
> 
> Just my 2 cents
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.