|
>From: "DeLong, Eric" <EDeLong@Sallybeauty.com> >Date: Fri, 19 Oct 2001 10:01:38 -0500 > >I'd probably look at grouping similar *svcpgm/*modules in binding >directories. Then, if you don't need the A/R modules for your program, just >don't add that bnddir to your program's h spec. I don't normally list >modules in the binding directory, as I'd rather keep them in a *svcpgm. >This helps keep your programs smaller. I would never put service programs and modules into the same binding directory. The risk in combining them is that you accidentally bind the same module into more than one program. Shudder. If you want to put modules into binding directories (I find it convenient to do that), then create a binding directory for each program or service program and put the modules for that object into its binding directory. (If you name the module binding directory the same as its object, it's very easy to manage.) Then in your command or H spec, just specify 2+ binding directories: the one with that program's modules, and the one(s) with the service programs. Barbara Morris
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.