Dave wrote on 14/09/2006 05:33:21 PM: > >I just did a quick count, I found 50 **.CSI.DATA files on my system. I > >have to get to the CORRECT SMP/E CSI before I can answer questions about > >proper maintenance levels. Maybe too many product installations start > >with "Create a new CSI".... > > That's a good point. > > With z/XDC, it having a command interface, I've implemented the > workaround. There's a LIST XDC command that displays the product's > maintenance level. > > Nevertheless, is it possible for me to: > - Integrate my CSI into the System's CSI, > - Yet still be able to create my own OPTIONS and UTILITY > definitions, > - Without affecting any other product, > - And without being affected by any other product? > - And still have a simple way to reset when something gets > botched up in SMP? (i.e. as if I did a delete and > rebuild of the CSI?) > If so, then maybe I'll revisit my requirement for a separate CSI.
- yes (doesn't need to be the "System's"; I generally have a THIRDPTY.CSI for example. - yes - probably - probably - maybe For you to have a clash with another product you would have to be unlucky, or stupid (especially if it's another of your own products). You may be unsurprised to learn CA qualify for the latter - with 2 of their own products. If one starts to get cute with SMP, it'll bite. I have on occasion had to resort to a full (DF/DSS) restore of the environment, and restart some aspect of maintenence. May not meet the definition of "simple" for some people - I find it no major impost. It should be noted I (almost) always ignore the demand for a separate CSI - mangling done at initial install is time well spent in our shop. Separate CSIs are built in need, as occasionally happens. Shane ... ---------------------------------------------------------------------- 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
