my current site is terribly averse to cloning, partly because
the security team (ACF2) do not know how to set the rules, and thus
do not want these additional tasks ...
- ravi.
R.S. wrote:
[snipped]
2) Share a volume between environments not protected via a integrity
manager like GRS or MII. One environment read/write, the other
read only.
#1 hasn't been a problem in a long time here, but I remember the days
when people constantly put their personal JCL libraries on the sysres
at other shops I've been at.
IMHO first reason is not reasonable. Uneducated people shouldn't be able
to allocate anything out of SMS. As additional resort of protection
mount attributes (STORAGE, PRIVATE, PUBLIC) and IGGPRE00 can be used.
The second reason could be real one, however personally I would consider
volume cloning (multiple copies) as an circumvention to sharing,
especially when important but relatively small amount of data is being
considered - I mean RES volumes. Two mod-9's is not a pain.
Just my $0.02
----------------------------------------------------------------------
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
