|
Hello, Rusty, again. When deciding about 1.st item, please pay your attention to security aspects. In my shop, we use an AUTL to protect the program library and an AUTL to protect DATA library (DATA can be deleted, while programs don't). Such a schema is simple and effective, for us. Sincerely Domenico Finucci Fiditalia , Milano, 02- 4301-2494 -----Messaggio originale----- Da: Rusty Luse [mailto:rluse@cronus.cc] Inviato: giovedì 3 ottobre 2002 16.15 A: midrange-l@midrange.com Oggetto: Library and Source File Question I am in the process of setting up some standards for creating libraries, source files, objects, etc. I have two questions that I would appreciate some help with. 1. Is there a major pitfall that I may encounter if I choose to setup a library that will contain all objects for a particular application? This library would include all program objects and data files. Should I separate my data files into another "data" library? Half of my coworkers think we should separate the data and objects while half think it is easier to keep everything in one library. What are the advantages and disadvantages? 2. This question is similar to the first question except it deals with source files. Many of my coworkers believe that we should keep all of our source in one source file instead of separating them by QDDSSRC, QCLSRC, QRPGLESRC, etc. I prefer to separate my source but am not against changing if one source file is better. Any suggestions? Thanks, Rusty _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.