On Tue, 11 Sep 2007 17:23:49 -0400, Bob Shannon
<[EMAIL PROTECTED]> wrote:

>>I can't justify a mod-27 since about 60% of it would be empty - multiplied
>by all our sysres sets: 2 for maintenance (one for each company), 6 for one
>company environment, 3 or 4 sets for 3 other environments and a few more
>sets for sandbox environments.  So at least 20 or so mod-27s in
>>all that would not even be half full.
>
>
>As I've said before, we define Mod-15s for the sysres. They're about 15Gb.
It's a good size for us. The entire sysres fits on 1 volume.
>

That's a good idea if you don't have disaster recovery implications.  We don't
any more, but we used to.   

The reason I don't want custom sizes is that occasionally we run out of 
available cloning sets and need to create a new one.  That doesn't ever
happen except during version migrations when some of the sets are 
used for one release and some for another.  But when it does, we can
easily get another set of 3390-9 volumes to use.   If we had a large
pool of say mod-15s in use for other workloads then that wouldn't be
an issue.   

We don't have many mod-27 volumes in use at this point, but we are
starting to use them more.   One of our sysres volumes contains
ISV products ("MVS" products only).   I could see using a mod-27 if we put
the ISV and IBM OS on the same volume, but I'm not sure I want to do that
(but I haven't ruled it out for the future either).

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Systems Programming expert at http://expertanswercenter.techtarget.com/
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

Reply via email to