I'm an application programmer, not a system programmer. One reason I use separate CSI is for testing installation of my products and PTFs. We tend to create CSIs as needed. This way I can play safely in my own little sandbox without messing the system up. At the same time, my resulting target libraries can still be made available to the other developers and testers who want to work with my libraries instead of the system libraries. The only complication I ever have for not being in the real CSI is that I must sometimes create some fake sysmods for my own zones to satisfy some pre-req conditions for things that aren't installed in my own CSI.
--Roger Bolan IBM Mainframe Discussion List <IBM-MAIN@BAMA.UA.EDU> wrote on 08/28/2008 02:08:23 PM: > On Wed, 27 Aug 2008 16:52:30 -0400, Howard Rifkind <[EMAIL PROTECTED]> > wrote: > > >Anyone out there familiar with the installation of the of the XML 1.9 > >product might be able to help me out with this. > > > >My manager wants this product installed in its own CSI. > > As far as I know it's not a separate product, but a part of z/OS. So I'm > curious why he wants it installed in a separate CSI. That seems likely to > cause problems when you install PTFs, or do upgrades of z/OS, etc. > > -- > Walt > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
