The problem comes in if the job that is being cancelled has control of a resource that is required for a higher importance job to run. Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Friday, December 01, 2006 5:39 PM To: [email protected] Subject: Re: Cancelling a job/tso user in a 100% CPU situation. >We end up having problems cancelling TSO users and test batch jobs. The CANCEL is accepted, but the address space cannot get any CPU to actually terminate. In what I humourously call my mind, this is a no-brainer (not having one makes this easy for me). Let'em rot! If they're not getting enough resource to cancel, they're not getting enough to run! So, they're doing nothing. Therefore, they're NOT a problem, and not interfering with anything. The problem comes down to the user not getting throughput/response. But, that's akin to: "Doctor, it hurts when I do this"! Dr: "Well, don't do that"! When in doubt. PANIC!! ---------------------------------------------------------------------- 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
