|
Agreed! So far I am the only one creating/adding modules. Very easy to manage. I have been adding new service programs and modules as the need arises, about 2 a month. We now have a second programmer versed in creation of modules, not service programs. Two more are going to take the seminar at Vegas in October. That is when I have to start managing the updating of service programs. Too much to do, to little time to do it all. With a new senior level programmer, hopefully some can be spread out. I am saving this thread for formal discussion on the whole change management issues. Thanks again for all your advise, Christopher K. Bipes Mailto:chrisb@cross-check.com Senior Programmer/Analyst Http://www.cross-check.com CrossCheck, Inc. 707 586-0551 x 1102 6119 State Farm Drive 707 586-1884 FAX Rohnert Park, CA 94928 ----- Original Message ----- From: "Simon Coulter" <shc@flybynight.com.au> To: <RPG400-L@midrange.com> Sent: Thursday, August 24, 2000 7:08 AM Subject: Re: Creating a service program M Hello Chris, You wrote: >I really was not worried about it, more curious than anything . We have been building >service programs and adding new modules to them for a very short time. The whole >re-compile thingy is growing to be a pain so I am playing with binder source. I could >see the service programs having modules added on a weekly basis as the other >programmers come up to speed in ILE. We could potentially have several layer of the >previous module list which would grow long and ugly fast. I wonder how well Hawkeye >will cross reference this for us and handle a mass re-compile? Need to investigate >tomorrow. I suspect you probably need to stage the creation of service programs. Rather than just wack in a new module or proc when the programmer completes it, save them until you have a few -- enough for a point release -- and put them all in together. You really don't want to be creating signatures for each procedure. Of course that all depends on how your development process is managed. Regards, Simon Coulter. «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» «» FlyByNight Software AS/400 Technical Specialists «» «» Eclipse the competition - run your business on an IBM AS/400. «» «» «» «» Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 «» «» Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au «» «» «» «» Windoze should not be open at Warp speed. «» «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» +--- | 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 +--- +--- | 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.