Someone else pointed out that xxxSTOP works for the RACF STC, where xxx is the subsystem identifier specified in IEFSSNxx.
In a larger shop, severely limiting access to *any* resource is problematic. If the installation needs 24x7 support, someone has to hold the key, and that someone has to be available to put it in the lock. I agree that too much access is a dangerous thing, but too little can be crippling as well. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Radoslaw Skorupka Sent: Tuesday, May 23, 2017 12:04 PM To: [email protected] Subject: (External):Re: RACF Database (was: Sample JCL for file transfer using NJE/TCPIP) RACF A/S can be easily stopped using STOP command (not an MVS STOP, it is @STOP). It also can be started again as well. The only cost is "address space unavailable" issue. Of course *properly protected* RACF db cannot be moved or deleted, due to lack of authorities. No one should have even READ to this profile. BTW: VSAM dataset can be read very early - see IODF file. Is it pure VSAM access method? Who cares! R.Skorupka (sent from mobile) BTW ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
