Is there no way to prevent journalling of these actions? Perhaps there
should be such a mechanism, perhaps under RACF control in the FACILITY
class. Perhaps a way to disable journalling a complete run of FIXCDS?
Sounds like a possible requirement here.
--
Rick
--
Remember that if you’re not the lead dog, the view never changes.
--------------------------------------------------------------------------------------
Adams, Rick wrote:
Rex,
I went through this same process a while back. I changed all of our
datasets to new management classes due to a new naming convention we
decided to implement. I generated the ALTER commands and issued them
1000 at a time (100 to a step). I had no issues with that process. The
only issues I encountered were that the BCDS Backup Version Record (the
C record) stores the management class name - thus if a dataset gets
recovered from a backup it will get the old management class - and the
MCDS Data Set Record (the D record) stores the management class name.
These need to be updated as well to allow your space management
processes to do the cleanup.
I originally altered the management classes in the catalog and then
deleted the original mgmtclas'. All of the non-migrated data worked
fine but the migrated data took errors during PSM due to the management
class being gone. I then went in and updated the C and D records using
FIXCDS and that solved the issue. Lots of commands and they will fill
up your journal if you are not careful!
HTH
Thanks....Rick
----------------------------------------------------------------------
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
