At 09:07 AM 9/24/97 -0400, you wrote:
>>>Also, at the sites where the clients have development
>>>libraries, there is such a disparity between the development
>>>side and the production side that if you move programs from
>>>dev to prod they will (dare I say it?) level check..
I think you mentioned that you can't get more DASD because of (politely called) budget reasons? That really makes this hard. Ideally you could have separate program & data libraries for development, integration testing (this is to prevent changes by other developers from affecting things you've completed), quality testing, and production. Since you probably don't have this (necessary) luxury, here's at least one thought--you don't need to duplicate test data in the production library (this assumes a separate library for production and development). Have test data in the development library and have empty files in the production library. This way, you can compile over the current versions of files, eliminating level check issues, without taking up too much extra space. One premise behind this is that the production library is reserved for distribution and normally would not have data, since each installation will have its own.
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
This mailing list archive is Copyright 1997-2019 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