Walt, Regarding the concern of stopping MIM, the LPAR where MIM is stopped is a SYSPROG only environment and MIM is not stopped in test or prod LPARs. Anyone taking the risk of stopping MIM understands the risk, is working alone in the LPAR and the stoppage is for a very short period. Don't worry about RACF, not applicable here (yes, I do have concerns about the security database in use).
Thanks, Paul >I would have expected that by stopping MIM you would lose multi-system >serialization, and at that point you would need to ensure that no jobs >or users were active on the system. And at that point you might as well >IPL. > >Are you working in a single-system environment as opposed to >multi-system? Or am I not understanding something else about your >environment? Or is this another scenario I should warn my colleagues >about that can cause corruption of the RACF database, so we can ask our >customers who use MIM about it on the rare occasion where they report >database corruption? > > Walt Farrell, CISSP > z/OS Security Design, IBM > >---------------------------------------------------------------------- >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 >========================================================================= ---------------------------------------------------------------------- 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
