> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Veilleux, Jon L > Sent: Friday, December 01, 2006 12:16 PM > To: [email protected] > Subject: [SPAM] RE: Cancelling a job/tso user in a 100% CPU situation. > > > McKown, John writes: > > 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. > > How about bumping up the priority of the job/tso user so that they can > get the CPU needed to abend? > > Jon L. Veilleux
HOW??? As I stated, for some batch jobs, that results in the SERVCLAS being updated when the restart and that is unacceptable. I guess that I could update the CA-OPS/MVS rule to only work if the CANCEL is against a TSO user. That's a good idea. I'll ask. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
