Michael, Hopefully I can help you with this. 1. This difference in catalog status is only a problem if you are retaining them by catalog in rmm. In all other cases, when the data expires and volume is returned to scratch the difference should be resolved. (depends on UNCATALOG parmlib option) To make rmm match the catalog you need to run CATSYNCH - this can be either done manually with EDGHSKP, or, use EDGUTIL to reset the CATSYNCH state to NO so rmm EDGHSKP automatically includes CATSYNCH next time it is run (The latter requires parmlib option CATSYSID(*) to be in use.
2. EDGHSKP requires rmm to be active. The only reasons to quiesce or stop rmm are: i) EDGBKUP with BACKUP(REORG), and ii) EDGBKUP RESTORE to the active CDS. 3. My thoughts about CDS percentage used are documented here http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2c8a0/17.7?SHELF=all13be9&DT=20110609111302 The answer to your question is 'it depends'! If you follow the recommendations I made in the rmm I&C Guide, including sufficient secondary space etc.. neither reorg nor percentage full are an issue until you run out of space in VSAM limits or available DASD space. Consider this - how much space in MB is 10% of your CDS? ..... How many data sets/volumes might fit in that space? ... are you growing in number of volumes/data sets .... Reaching an limits? Mike Wood rmm expert ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
