Pros: Cheap Cons: Higher risk to production data being copied/misused. Cons: Higher risk to production data if test programs used against it. Cons: Serious complaints from internal/external auditors. Cons: Potentially violates segregation of duties. Cons: Potentially violates "need to know" access levels. Cons: Complicates security rules. Cons: Complicates naming conventions for datasets/programs/CICS regions. Cons: Complicates/Compromises security over program change control. Cons: Testing can sometimes slow down production processing (esp. CICS). Cons: Can cause failure of PCI, HIPAA, SOX and DIACAP rules/regs. Cons: LPAR crash kills all work for both prod and test users.
Hope this helps. Many thanks. Doc Farmer Senior Security Specialist InfoSec, Inc. http://www.InfoSecInc.com http://www.linkedin.com/in/DocFarmer http://tinyurl.com/2t6bwd (Click to Connect) On Tue, 8 Sep 2009 19:39:56 -0500, gsg <gsg_...@yahoo.com> 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
