1. It's not specific to ACF2. 2. It doesn't let you control the SYSOUT class.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Anthony Thompson <[email protected]> Sent: Wednesday, March 4, 2020 12:01 AM To: [email protected] Subject: Re: JES2 - stopping users from sending output to specific outputclass Jantje pointed out what seems the sensible solution, use the ACF2 JESSPOOL resource class: https://secure-web.cisco.com/1SQs1JP1i-71OzMTZOyJFk-Fu5Hli_ATR82-cxTH5N_aW0Lczz4WvGRG4FBmWvzBP3087MsMi6_C9wqFDS9KfRcCqch2aiMkSUbUdZZyHHN0-l-6n4ik5y_gAErMgoXy8HyxTCel5DAmToJE1szhId5UPfmMo_Q5cB9qA8N9nPG8dw52xEKR8KHBQhi5MyECsDM_vWSHccZPX-VbT7lG1G48H8vn-LnaFLv6n63g9jPKwnfUJTxvrwucmxj9v4dGcQL4EBqRWaliBegI_0VTZEUiIy9IHj5g-71TeIRN2s_WrvdAuH-HktViZMfWpZyl1G6HIGmwi-6mrIuoE8vhDvmfZzqdrJMHux23iK-whj8rjcgzBt54Rg4YinH0tWSgYCo09IciuqhDWVElygnUNbGJLhwIkmgOa4lnmIK7QgkPX_7r9KX9_deN7TxsKOu20/https%3A%2F%2Ftechdocs.broadcom.com%2Fcontent%2Fbroadcom%2Ftechdocs%2Fus%2Fen%2Fca-mainframe-software%2Fsecurity%2Fca-acf2-for-z-os%2F16-0%2Fadministrating%2Fjes-security.html Using JES(2?) exits might be too much: not many shops like exits these days since then they need to employ clever sysprogs that know assembler to maintain. I'll point out that as of z/OS 2.4, IBM have begun introducing JES2 Policies intended to replace JES2 exits. Another more trivial solution might be to restrict to a certain privileged set of users the ability to view that SYSOUT class via SDSF using ISFPARMS/PARMLIB(ISFPRMxx). Others would probably stop using that class if it doesn't do them any good. Ant. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Keith Costley Sent: Tuesday, 3 March 2020 7:33 AM To: [email protected] Subject: JES2 - stopping users from sending output to specific outputclass We are having an issue with users using a restricted output class based on standards. We are looking for a way to prevent this from happening by canceling the job if the JCL contains SYSOUT=X. We are an ACF2 shop but I am unaware if ACF2 security can limit this through a security definition. The other option is a possible exit. Has anyone done this in the past and has a suggestion on the best approach? Thanks, Keith Costley ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
