-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Friday, December 01, 2006 10:50 AM To: [email protected] Subject: Cancelling a job/tso user in a 100% CPU situation.
This has come up here. We are in month-end. Our CPU resource is 100% pretty much constantly. And, even worse, with a CPU Queue Depth of over 20. 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. <snip> What a co-inky-dink. I was just giving this situation some thought this morning. I used to have a utility routine that would do a CALLRTM and terminate a JOB/TASK with the Sxxx I desired. Seems that this is how RESOLVE did it back when I was at Droole & Babble (as I recall it forced a S222). But, this then comes back to the question, under WLM, will the target JOB/Task get CPU to be terminated? I would think it does because the MVS CANCEL command handles this a bit differently if I remember correctly. Perhaps you could write the same and get it blessed? Later, Steve Thompson ---------------------------------------------------------------------- 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
