Thanks! DSPAUTH=AMSG is what I was looking for. I realize that SAF is a 'better' way to go, but it's also more arduous. We don't currently use SAF for SDSF; turning it on would amount to a 'project'. Adding AMSG to selected users could fly as a tweak to the current environment. I'll try to sell it.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of retired mainframer Sent: Monday, September 12, 2016 2:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Limiting SDSF browse to JES datasets In the SDSF Operation and Customization manual, it looks like DSPAUTH=AMSG and related parameters may allow you to do what you want. But it seems like SAF (at least RACF) provides much better granularity and in an easier to understand format. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Jesse 1 Robinson > Sent: Monday, September 12, 2016 2:06 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Limiting SDSF browse to JES datasets > > For the first time, I'd like to allow users to browse job output but > limit the scope to just JES > data sets: log, JCL, job messages. I've cast about in KC but don't see > an appropriate option. > I'd like to use just ISFPRMxx if possible. I.e. not SAF and not user > exit code. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
