OK, I will fan the flames. >Although one has to be careful on what you do in an SVC screening >routine,there are legitimate reasons to intercept an SVC.
Just because your application wants to do something does not mean that you have a legitimate (supported by IBM if what you do according to the documentation breaks the system) reason to use a service for other than its documented intent. I concede that there might be legitimate reasons to front-end an SVC, and SVCUPDTE is provided for that mechanism (you certainly are not allowed to change the SVC new PSW). SVC Screening is not documented as a means to do what you write. That isn't to say it could be used to do that. For the case mentioned, was it truly SVC Screening that was used (as that would have required modification for each TCB to be monitored) as opposed to SVCUPDTE? SVCUPDTE seems more likely, and is more in line with "swap your own FLIH". 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
