ibm-main wrote:
From: "R.S."
While the answer is simple:
..
3. You can protect the volume by protecting every dataset on it, and
protecting the volume from new datasets creation. First is being done by
creating DATASET profiles (it is not hard job, unless you have mess),
Useless (as in totally nonfuntional) for indirectly catalogued datasets.
These are generally resident on the only volumes in the shop you want to
make "read only" - for example to protect the production copies of SMP
targets that get hit during system updates.
Please, sched some light on me. What cataloging (direct or indirect) has
to do with dataset profiles ? If one really wants to have given volume
read only, it is quite easy even to list every single dataset on the
volume and assign even discrete profile. DCOLLECT + some rexx code would
do it.
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
