|
MCPARTLAND, Stan wrote: > Like Dan, I'd like you to expand on your reasons for avoiding a single > source file. With the tools available today, I can't come up > with a single > reason to use multiple source files. PDM and WDT (CODE/400) are both much > more effective tools when used with a single source file. Source files by > source type is just a "legacy" practice that was encouraged by > the System/38 > Programmer's Menu. I agree that things such as division of duty, > security, > and backup and recovery should be considered when designing an > application's > landscape, but I don't see how source type has an impact. > We still use multiple source files. I guess that part of the reason is that we're used to have it that way since the S/38 days, but some of us still use the programmers menu (!). We have implemented an exit program to add extra parameters to the CRT* commands - (like bndsrvpgm) stored in source comments in the beginning of each source. We could probably have used user defined options in PDM in stead... Another reason is that restore of members (if one should need it) takes a *long* time when thousands of members are placed in the same source file. +--- | 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.