|
I guess my question sparked more debate than I really intended.... What I was looking for is when do you decide something is right for a subprocedure or is it just so menial that it is silly to do this. My main focus is that the higher ups are talking about doing a rewrite of our system..... Most of the code is old (many of the dates in seu are 87 88), no use of copy books, no vendor software (all in house). example 1: Payroll system we have a program that creates a list for payroll personnel of who is going to be paid, how much and so on. The actual program uses the axact same code to actually write checks but in a different source... Obviously the problem here is that when some thing changes we have to change 2 seperate source file and recompile blah,blah,blah. This seem perfect for using subprocedures/service programs in a rewrite.. example 2: we want to standardize interfaces across the system. is it worth it to create service programs to handle the screen interface or is this just an extra level of complexity that would get in the way? +--- | 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 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.