I think that by having one LPAR run both test and prod will impact the down
time for your Prod applications to doing system maintenance testing.
Realize that when you share everything in on LPAR then all things at risk
when doing system maint.
For example, CATALOG maint, DFHSM maint, anything hitting LPA or Nuc will
probably require an IPL. If your environment is such that the production
systems must be available, then you will not be able to do system maint that
requires an IPL very frequently. Next you have to setup a testing window
and have PROD down so you can verify your system maint without causing a
problem to prod. This can be tricky depending on what maint is to go in.
They you have to back it out after testing to ensure that prod is the same
as before the test. And you also have to consider your application test and
development folks for your testing windows as well. You cannot keep them
from their work for very long.
By having separate LPARs for test and prod you can test on the TEST lpar
more easily. Especially if you keep the catalogs (especially MCAT)
separate, and possible have separate HSM and network connections.
Auditors do not like having a TEST and PROD system share anything. That
could allow someone with bad intent to compromise your production data by
having access to it. By keeping it as separated as possible, then your
reduce the risk to your production processes.
Some questions you should consider are:
1) If they are on the same LPAR what is
a) My test window going to be like. How do I affect production and
application dev/test?
b) When do I roll maint for my system or subsystems
c) What are the risks when installing new function
d) What are my SLAs or Management requirements
e) What is the roll out process from TEST to PROD? How many system
files should be shared and which ones should not be shared.
2) If they are on 2 LPARs what are:
a) How separated can I make the LPARs
1) Separate DASD?
2) Separate Network connection
3) Separate Subsystems (CA1, SMS, DFHSM, Catalog)
b) Will TEST have PROD dasd online
c) Will TEST be part of a Shared Catalog (Both use the same MasterCat)
d) Will there be application devl/test groups in this LPAR
e) Will there be sufficient usage of this TEST LPAR to justify it
(licenses costs, CPU utilization)
f) Will the TEST lpar have an impact on Prod LPAR if there is a run
away task?
I am sure others will have many more thoughts than these.
Personally, if I can keep it separate and management is okay with costs and
such, then I prefer separate. Otherwise maint and testing can be very
challenging.
Lizette
> gsg wrote:
>
> Can everyone share some Pros/Cons on having seperate LPARs for Prod and
> Test and also Pros/Cons for having a single LPAR that Prod and Test will
> share. All feedback is welcome.
>
> TIA
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
