×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
90% of my customers use separate LPARs for the development, QA and
Production environments, although most only have Dev and Prod. They do
QA on the dev machine with library lists.
The customers with one or two folks in the IT department tend to do it
all one one LPAR.
Because SOX requires separation of duties and authority it's not
practical to have only one LPAR. I doubt you would pass an audit that
way, but I suppose it could be done but geesh it would be a real
challenge to set up.
Maybe your iSeries is a problem for a 10 year old machine but IBM i
running on Power is anything but antiquated and has passed many SOX and
GAAP audits.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 9/4/2013 3:38 PM, Stone, Joel wrote:
What constitutes separate DEV, TEST,& PROD environments at your organization?
Must they exist on separate LPARS? Separate boxes?
Or can they all exist on one LPAR with adequate border fences?
Would it be practical to exist on one LPAR and still comply with SOX and GAAP and a typical big auditing company's security audit?
Or is that not possible in the Iseries world with the antiquated only one level of libraries and such?
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.
midrange.com
