On Thu, 14 Sep 2006 03:33:21 -0400, David Cole <[EMAIL PROTECTED]> 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"....
>
They may say that, but if you have some experience you can create the
target / dlib zones in an existing CSI / global zone if you wish. Some
vendors already give that option (one global zone per vendor).
Personally, I prefer having each ISV product / release in its own
CSI that follows the same naming convention as all the tgt / dlibs
and smp/e data sets. When I install a new version or get rid of the
product completely, it makes it *real easy* to trash the whole thing -
DELETE HLQ.VEND.PRODUCT.VERSION.**)
I have also been using a small ISPF appl for years that reads a list
of global CSI data set names and descriptions from a flat file (which
is a PDS member in my case) to pull up a menu for invoking SMP/E
using the selected data set as the global zone. It can also be invoked
with a filter parm - TSO %SMPSEL Z/OS. I think it originally came
from one of the Xephon pubs, but I modified it (which is why I don't
have it on my web site / CBT file).
>If so, then maybe I'll revisit my requirement for a separate CSI.
I wouldn't do any more than say it's optional and samples need
to be modified to install into existing zones. I can't think of any
other ISV products I've installed in recent years that need a CSI that
don't supply jobs to create an SMP/E environment for you. This wasn't
true in the past - especially with IBM program products. They gave
you printed samples in the PGMDIR. This led me to create my generic
jobstreams that can be found on my web site / CBT file 434:
SMPBLD1 - Job to build an SMP/E environment from scratch.
All VSAM SMP/E zones are created within the same
physical VSAM data set.
SMPBLD2 - Job to build an SMP/E environment from scratch.
The VSAM SMP/E zones are created as separate
physical VSAM data sets.
SMPBLD3 - Job to build a new SMP/E target zone, dlib zone,
and other required SMP/E data sets into an
existing global zone.
Anyway... I can't imagine why someone would want to install your
product into another vendors CSI, but each to their own. Many years
ago I remember being in a few shops that had one huge global zone
for many different vendor products. I haven't come across a shop
that does that still in a long time.
Regards,
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group
mailto: [EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
