I trust you've explained to your management that by not putting the initiators under WLM control that they are exacerbating the problem. Once you reach 100%, each additional submitted job takes cpu cycles away from Problem State because the operating system needs the cycles in Supervisor State to manage the additional workload.
Unfortunately users would rather see their jobs 'running' even when they aren't receiving much, if any, service, than sitting in the input queue. Your management has 3 choices: Manage the workload Upgrade the cpu Accept the situation -----Original Message----- From: McKown, John [mailto:[EMAIL PROTECTED] Sent: Friday, December 01, 2006 1:51 PM To: [email protected] Subject: Re: Cancelling a job/tso user in a 100% CPU situation. > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock > Sent: Friday, December 01, 2006 12:30 PM > To: [email protected] > Subject: Re: Cancelling a job/tso user in a 100% CPU situation. > > > How is that remembered after a $CJ? I would think the new job should > have be assigned its service class based upon the > WLM rules. > > > Jon The $EJ and $HJ before the $CJ causes that __same__ job to be requeued to be re-executed. During the re-execution, the job runs with the non-standard "high" service class that the CANCEL (which the $CJ issues "under the covers") rule in CA-OPS/MVS uses to issue a RESET. -- 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 ---------------------------------------------------------------------- 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
