I hope that this SVC has been removed. These "super-secret" SVC's are nothing more than MASSIVE integrity exposures, that can be relatively easily spoofed, and should be banned from any and all z/OS sites.
=============================================== Wayne Driscoll OMEGAMON DB2 L3 Support/Development wdrisco(AT)us.ibm.com =============================================== From: "Emily A. Rambo" <[email protected]> To: [email protected] Date: 04/22/2011 11:27 AM Subject: Re: Mixing Auth and Non-Auth Modules Sent by: IBM Mainframe Discussion List <[email protected]> If there's no way to get what you need without using the functions that IBM requires be authorized, here's another possibility. We had a sysprog years ago who coded a user SVC that could be called to flip the JSCBAUTH bit on or off, with a very short list of program names in an internal table that are allowed to call the user SVC. It was needed for a dynamic allocation common module (SVC99) because IBM required that the caller be authorized in order to code the WAIT FOR UNITS parameter. We were having a lot of contention with tape drives at the time (pre virtual tape days). The dynalloc module called the user SVC to get itself authorized if wait for units was requested, it issued the SVC99, then called the user SVC again to de-authorize. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
