I create a non-RACF CP nuc for cases where we would not be able to start-up RACFVM, nor RACMAINT, so SETRACF INACTIVE would not be possible. (e.g. RACF DB on 200 & 300 damaged). We never needed it since we started with VM about 18 years ago.
*Alan Altmark <[EMAIL PROTECTED]>* wrote:
If anyone cares, you can CP SEND RACFVM SETRACF INACTIVE. This will cause the CP-resident RACF code to begin to defer all requests back to CP, as though RACF is not present, including LOGON. You don't have to deactivate any classes or change any permissions. No auditing is performed. RACF will, however, prompt the OPERATOR for confirmation. A SETRACF ACTIVE will start the wheels turning again and the OPERATOR will be informed (but not prompted).
-- Kris Buelens, IBM Belgium, VM customer support
