-------------------------<snip>-------------------
OK. You present a cogent case for the customer's not installing ISV
products into the z/OS CSIs. But if the customer chooses to be so
imprudent, there's little the ISV can (or should) do to forestall it.
Sprinkle in a few NPREs for selected IBM FMIDs? I think not. But, yes,
supply tailorable JCL that does not presume installation in z/OS's CSIs.
But is there yet a desire for placing the ISV's TARGET and DLIB zones in
CSI(s) separate from the ISV's own GLOBAL zone, or am I misreading
between the lines?
--------------------------<unsnip>--------------------------
Since I'm usually maintaining multiple images, I almost always separate
the target zones in separate CSI's from the GLOBAL zone. Separating the
DLIB zones into separate CSI's depends on GLOBAL ZONE CSI space
considerations; if the CSI starts expanding too fast, I might break out
the DLIB zone(s).
---------------------------<snip>------------------------
Does declustering zones into separate CSIs have any effect on the
proliferation of SMPTLIBS?
---------------------------<unsnip>---------------------
Note that I've ever noticed. They belong to the GLOBAL zone. But by
assigning a separate GLOBAL zone, I can assign different names and
thusly different SMS attributes; This allows me to better control where
they're allocated.
----------------------------------------------------------------------
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
