Not all shops use SAF to control SDSF. If so, this advice is fine. If still using native ISFPARMS, the approach will need to be different, including some tweaking of the SDSF user exit if used. I'm surprised that any action at all is necessary for a user's own jobs...
. . 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 <[email protected]> On Behalf Of Charles Mills Sent: Thursday, March 12, 2020 2:07 PM To: [email protected] Subject: (External):Re: JESSPOOL CAUTION EXTERNAL EMAIL A *very* crude approach is to look at any RACF violation message on the console and translate that into a PERMIT command: PERMIT resource CL(class) ID(id) ACC(acc). There is typically a resource, a class and the access in the messages. You may have to apply some "intelligence" -- for example, if your shop may prefer to give permissions by GROUP rather than by individual userid. Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
