This is a RANT, reasonable persons should disregard.
We are involved with, for us, a BIG project.
1,000's of man-hours, 1,000,000's of $...
We are using our test lpars in what I think is a perverse and
twisted way:
1) changing production library lists to use test libraries
2) in some cases, removing a production library from the lpar
3) not taking the trouble to: a) discuss or advertise this b) not
taking the trouble to ensure all test libraries are ready for
serious use
My advice to anyone contemplating use of test lpars is to "forget"
the "test library concept" and maybe consider purging them from the
lpar.
BTW, I started attempting to be a "programmer" before computers
had lpars and started with the test library concept as the only "test
environment" available to me. Actually I started on a COBOL/MVS
system that had only the production and test MVS instances but, if
memory serves, only one instance of program objects.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.