On Thu, 21 Sep 2023 06:50:01 -0500, Michael Babcock <bigironp...@gmail.com> wrote:
>Thanks Rob! That’s the explanation I needed! However, I did create a >ISF*.** profile with a UACC of ALTER but it still didn’t work because I >didn’t have NOFAILRC4 (I assume). > >On Thu, Sep 21, 2023 at 2:52 AM Rob Scott <rsc...@rocketsoftware.com> wrote: > >> Michael >> >> Although we strongly recommend JESSPOOL (and OPERCMDS) being active, you >> can use successfully use SDSF without it. >> >> The big difference in z/OS 2.5 is that SDSF will no longer fall back to >> any legacy ISFPRMxx authority keywords on the GROUP statements when SAF >> returns RC=4. >> >> How SDSF handles SAF RC=4 (returned when the ESM cannot make a >> determination - for example the class not active or no matching profile) is >> governed by the AUXSAF(FAILRC4/NOFAILRC4) keyword on the CONNECT statement >> in ISFPRMxx. >> >> The default value of FAILRC4 means that SDSF will translate RC=4 from SAF >> into a "denied" response, whereas NOFAILRC4 will translate to "allowed". >> >> So you could keep JESSPOOL inactive and use AUXSAF(NOFAILRC4) on your >> rescue system ... <snip> If this happens to be a modified version of my onepack JCL from my web site / CBT file 434, when I put out the z/OS 2.5 version it will have CONNECT AUXSAF(NOFAILRC4) in the ISFPRM00 member that is supplied by default. Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
