>Curious: Does anyone use SVC screening for its documented intended >purpose: to define those SVCs that a particular task is allowed to issue >(and conversely those that it is not allowed to issue)?
I intentionally phrased the question the way I did, although no one answered it in that spirit. The answer, based solely on the posts so far, appears to be "no". There are a lot of other entertaining, interesting, probably useful, but nevertheless wholly unsupported, uses that have been found for SVC screening. I do mean to provoke thought; I do not mean to cause alarm. As long as the SVC screening routine does everything right, so that the user gets what the user should get in all cases, I don't have overly much problem with this misuse. But very often that is not the case, including functional problems or even system integrity problems, related to examining the user parameters or due to making the SVC appear that it had not come from the user who actually issued it. Note that users who use SVCUPDTE to front-end SVCs often inject similar problems. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
