|
I can see that, Scott. What I would like to have done was include the GENERAL service program inside of the CARTAGE service program, but that doesn't seem to be doable. But then when the General was updated so would the Cartage, or at least it would error out or something. I don't like the idea of compiling with more than one service program, however, and am not even sure if it's possible. That is a viable alternative however I suppose. Regards, Jim Langston Programmer/Analyst Cels Enterprises, Inc. -----Original Message----- From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On Behalf Of Scott Mildenberger Sent: Wednesday, August 29, 2001 6:55 AM To: 'rpg400-l@midrange.com' Subject: RE: Procedure Management Procedures In the example below I would create 3 different service programs. I don't like th idea of a module being put into more than one service program, it just increases the chance that something doesn't get updated when a change is made. We only bind a module into one place, it is either to a single program or into a service program if it is used more than one place. As much as you can use bind by reference (using service programs) then it eliminates the chance that a program is using the wrong version of code. Scott Mildenberger > -----Original Message----- > From: Jim Langston [mailto:jlangston@celsinc.com] > Sent: Tuesday, August 28, 2001 3:18 PM > To: rpg400-l@midrange.com > Subject: RE: Procedure Management Procedures > > > For the small service programs I had with about 25 procedures > total in one service program I added all 3 of my modules, in the > other I added 2. The 3rd module was specific to a certain > application, the other 2 were generic. > > So, I had modules: > DATETIME (Date/Time routines) > SYSTEM (System API call interfaces) > CARTAGE (Specific to the Cartage application) > > Service program CARTAGE contained all 3 modules. > Service program GENERAL contained DATETIME and CARTAGE. > > So if I was writing a Cartage program I would use the CARTAGE > service program. If I was writing any other program, I would > use the GENERAL service program. > > I am not sure if this is the proper way to do it, but I felt it > was the best at the time. > > Regards, > > Jim Langston > Programmer/Analyst > Cels Enterprises, Inc. > > -----Original Message----- > From: rpg400-l-admin@midrange.com > [mailto:rpg400-l-admin@midrange.com]On > Behalf Of Bill Meecham > Sent: Tuesday, August 28, 2001 12:49 PM > To: RPG400-L@midrange.com > Subject: Procedure Management Procedures > > > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Hello All - > In an ILE environment what are you folks doing to manage the > procedures that you have created? Do you keep all of your procedures > in 1 service program? How do you track the names and what > they do, with notes in the prototype file? Are you using > modules as well > as procedures in programs? Are you using modules in procedures? > I'd just like to get an idea of how folks are managing these > things and what some of the development environment models are like. > Thank you! > Bill M > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) > mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.