|
Application Binding Directory? I think you're referring to Binder Source. The source file/member that you specify on the CRTSRVPGM menu. Thanks, Mark Mark D. Walter Senior Programmer/Analyst CCX, Inc. mwalter@xxxxxxxxxx http://www.ccxinc.com daparnin@coopersta ndard.com To: rpg400-l@xxxxxxxxxxxx Sent by: cc: rpg400-l-bounces@m Subject: Re: Service Programs 101 / Binding Directories idrange.com 07/23/2004 01:01 PM Please respond to RPG programming on the AS400 / iSeries Can open, worms out. I knew that it seemed too good to be true! I knew that it couldn't be that easy!!! <g> OK, let me take a stab at the concept behind having an application binding directory *and* a development binding directory/directories. Is the application binding directory so that the application program can find a service program and the development binding directory is so that the compiler can find the modules to be combined into a bound program or service program? Dave Parnin Nishikawa Standard Company Topeka, IN 46571 daparnin@xxxxxxxxxxxxxxxxxx Buck Calabro <buck.calabro@comm To: rpg400-l@xxxxxxxxxxxx@SMTP@CTB soft.net> cc: (bcc: David A Parnin/Topeka/NISCO/SPCO) Sent by: Subject: Re: Service Programs 101 rpg400-l-bounces@m idrange.com 07/23/2004 08:16 AM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@midrange .com> Wayne James wrote [about binding directories]: > Since they are not *just* for service programs, > I tend to want to create a binding directory for > *building* my service program (listing the > *MODULEs required) and then add the service > program to an "application" binding > directory where it will be *used*. Absolutely, absolutely right. When someone is just starting out, I advise one binding directory (what you call an 'application' bnddir - nice name!) because it's easier to introduce one new concept at a time. When they move into creating complex multi-module service programs, I tend to advise either a 'make' program rather than compile/bind separately -or- a separate bnddir for each complex service program. > There are very valid arguments for the single > "application" binding directory, but having only > one binding directory for everything is, IMHO, > a *bad thing*. While I generally agree, there is one reason for 'one bnddir for everything:' it enforces very strict organisation. Procedures _MUST_ be named so that there aren't any duplicates (like getName in the customer service program and getName in the vendor service program.) Procedures _must_ go into one module and only one module. The downside of 'one for all' is that you can't be as flexible in your design... Nice addition to the thread, thanks! --buck -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.
midrange.com
