David Cole wrote:
At 9/13/2006 03:32 PM, LRugen wrote:
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.
I don't have a problem with multiple CSIs as long as there a a minimum
of Global CSIs. At a previous client, we had only "1" Global CSI, with
one or two CSIs per vendor/product. The Target/DLIB CSI naming
convention made it relatively easy to locate a specific vendors CSIs.
Then it is possible to have your own OPTIONS and UTILITY definitions
without impacting or being impacted by any other product.
Dave, your maintenance strategy of restore prior to apply, could better
be served by a single maintenance sysmod that contains all prior
maintenance and SUPS all the potentially applied and accepted sysmods.
Someone else may have suggested that during this thread.
Paul Gillis
----------------------------------------------------------------------
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
