In regards to JES2 SPOOL volumes without VTOC index:
On 31 Mar 2006 02:22:05 -0800, in bit.listserv.ibm-main
(Message-ID:<[EMAIL PROTECTED]>)
[EMAIL PROTECTED] (R.S.) wrote:
Vernooy, C.P. - SPLXM wrote:
Valid reasons, however our spool and page pack do have
indexes, just because of the rule: one size fits all. One
initialization procedure for all avoids having to think
and possibly make errors. What is a few tracks in a
Terabytes Dasd configuration?
It does make a sense, however I'd prefer "two sizes" - not
to many, not individually assigned for every volume. I
don't consider it as error prone, since:
1. It is done by wise admins, not dummy enduser.
2. Vast majority of volumes are under SMS, the only
difference is because of volume size (mod3, mod9, mod27).
All "special" formats are solely for system volumes, like
SPOOL or PAGE. Special format is done under special
caution - it isn't done day by day.
This brings up a question: Is a one-size-fits-all
solution correct if you have a mix of 3390-3 -9 -27 -??
DASD? DASD is (fairly) cheap now, but does it really make
sense to put a 3390-27 sized VTOC and index on a
3390-3? Or, does the "one size fits all" philosophy also
restrict you to one size of disk?
I half-like Vernooy's comment about *one* procedure
to avoid errors and having to think. Automating something
right means it's done correctly from then on, with no
finger checks. I've found very few cases, though, were not
thinking when "there's no need to think" hasn't caused
trouble, eventually.
----------------------------------------------------------------------
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
