I am sure that there are even alternatives to the STATUS STOP technique if something *must* be done.
Off the top of my head, how about issuing a WTO or WTOR that gets picked up by your auto-ops tool that then either QUIESCEs the address space or puts it into a discretionary WLM service class. The operators can be alerted and can then take action on the affected address space if required to restore its former glory. Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] http://www.rs.com/portfolio/mxi_g2 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Craddock, Chris Sent: 15 January 2007 19:10 To: [email protected] Subject: Re: Status Stop and REXX > I'm trying within IEFUTL Exit to stop the address space (all other TCBs) > from working; because in certain circumtances I'm asking the operators > (WTOR) to decide if the address space have the right to use more CPU. > > To do this I use the status stop macro and it works fine... but not with a > batch TSO Rexx programm; this one (only this TCB) is running and running. > Using a SVC Dump I've seen, that the TCB Stop is delayed. > Does someone have an idea how to even stop such a TCB? What you're trying to do is pretty dangerous and the risk is certainly not outweighed by the little bit of cpu time that might be consumed while you ask the operator. In this day and age why should you even be thinking about stopping the user's use of the resource unless they asked you to? They are typically the ones who pay the bills. CC ---------------------------------------------------------------------- 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
