"Magic" SVCs are the scourge of z/OS integrity. The amount of validation you have to do to make a magic SVC airtight exceeds the burden of simply doing it right: linking the program AC=1 into an APF-authorized library.
They used to be common in vendor products: easier to write a magic SVC than to get the customer to authorize the library. I think the practice is on the decline. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Thursday, May 18, 2017 8:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ATTACH with RSAPF=YES Early versions of SDSF provided an SVC that would make the user authorized. It was 'supported' in that it was part of an official IBM program product. There was a general discomfort with this strategy even though the SVC code tried very hard to validate the environment. Eventually (I believe) the SVC was discarded as being too difficult to make airtight. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
