1 level or more levels really DOESn't matter, seems to me. In any case, there have to be different names. Does it matter whether those names are side-by-side or top-to-bottom? Not really.
So a method at one time - and still useful when you don't have multiple LPARs (or even if you do) - is use libraries and users that have some identifier for each environment. Hey, a library list and a path are basically the same concept, right?
As to "slamming" - you were the one to use the word "antiquated". To me that's a slam. Personally, I see no problem with this file system. And if you have a decent change management system, it is all done for you with paths (library lists) and appropriate authority.
JMHO at the end of a long day! Rehearsal to follow - too much fun!
----- Original Message -----
"I fail to see how having only 1 level of libraries matter. "
One level of hierarchy seems antiquated in that all other OS's allow many levels.
For example, any other OS could have the following folders:
JDE 9.0 containing program lib + data lib + config lib etc
JDE 8.0 containing program lib + data lib + config lib etc
SAP 2.0 containing program lib + data lib + config lib etc
Lawson 3.0 containing program lib + data lib + config lib etc
It doesn't seem possible to do this on iseries as a library cannot have a hierarchal group above or below, only one level is allowed. So people use multiple LPARs or boxes to get around this constraint that doesn't exist on other OS's.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Wednesday, September 04, 2013 4:05 PM
To: Midrange Systems Technical Discussion
Subject: Re: separate DEV, TEST, & PROD environments survey
I've worked in all three types...just depends on the size of the company.
I fail to see how having only 1 level of libraries matter. For that
matter, every single RDBMS I'm familiar with only allows a single level of
Once the shop gets big enough, separate LPARs or boxes is probably most
On Wed, Sep 4, 2013 at 4:38 PM, Stone, Joel <Joel.Stone@xxxxxxxxxx> wrote:
What constitutes separate DEV, TEST, & PROD environments at your
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?
Thanks in advance!
This outbound email has been scanned for all viruses by the MessageLabs
For more information please visit http://www.symanteccloud.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives