|
<snip> A little juggling of the library list gives complete isolation from production: LIVE ENVIRONMENT: DATALIVE PROGRAMLIVE ... TEST ENVIRONMENT: DATATEST PROGRAMTEST PROGRAMLIVE ... </snip> I have to point out that at V5R2, Independent Disk Pools eliminate the need for these types of library lists. You can completely segregate the different environments and move between them without having to manipulate job descriptions and library lists. Security is also greatly enhanced. Programmers can still see the data without signing on to the production environment, (using SQL) so they loose the one primary complaint the use. We have the ability to test the actual object in the actual environment it will run in. That should be a compelling case to at least investigate the use of the new tools we have. One more thing, IDPs set up the system up for clustering. Along with an LPAR, that will allow a properly set up system to run 24*7*365 without much if any downtime, HA software optional unless an HA environment is needed. Jim Oberholtzer Senior Solutions Architect Computech Resources, Inc.
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.