Re: separate DEV, TEST, & PROD environments survey

> On 9/4/2013 5:42 PM, Stone, Joel wrote:

...(snip)...
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:

PROD env
-----
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

TEST env
------
Ditto above

DEV env
-----
Ditto above

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.

Huh? You could easily create libraries named, for example, as follows:

PROD env
--------
JDE 9.0: JDE9.0PGM, JDE9.0DTA, JDE9.0CFG
JDE 8.0: JDE8.0PGM, JDE8.0DTA, JDE8.0CFG
SAP 2.0: SAP2.0PGM, SAP2.0DTA, SAP2.0CFG
Lawson 3.0: LAW3.0PGM, LAW3.0DTA, LAW3.0CFG

TEST env: (suffix "T")
--------
JDE 9.0: JDE9.0PGMT, JDE9.0DTAT, JDE9.0CFGT
JDE 8.0: JDE8.0PGMT, JDE8.0DTAT, JDE8.0CFGT
SAP 2.0: SAP2.0PGMT, SAP2.0DTAT, SAP2.0CFGT
Lawson 3.0: LAW3.0PGMT, LAW3.0DTAT, LAW3.0CFGT

DEV env: (suffix "D")
--------
JDE 9.0: JDE9.0PGMD, JDE9.0DTAD, JDE9.0CFGD
JDE 8.0: JDE8.0PGMD, JDE8.0DTAD, JDE8.0CFGD
SAP 2.0: SAP2.0PGMD, SAP2.0DTAD, SAP2.0CFGD
Lawson 3.0: LAW3.0PGMD, LAW3.0DTAD, LAW3.0CFGD


Or you can devise some other naming conventions, such as:


PRJDE90PGM, PRJDE90DTA, PRJDE90CFG
TSJDE90PGM, TSJDE90DTA, TSJDE90CFG
DVJDE90PGM, DVJDE90DTA, DVJDE90CFG

etc.

There is plenty you can do with 10 character names.

Mark