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.
We used to have a CA-OPS/MVS rule to do a RESET ...,SERVCLAS=.... to set the cancelled address space to a very high priority service class. Unfortunately, this has resulted in another problem. We use CA-MIM Integrity to requeue work which has ENQ conflicts on datasets. CA-MIM does this via a $HJ/$EJ/$CJ sequence. The $CJ results in the service class being reset to the high priority one. But it is "remembered" and is used when the job next starts to execute. This is unacceptable, but I cannot think of a way around it. So, any words of wisdom that don't boil down to "don't do that!" WRT to overinitiating the CPU? I cannot control that. Well, I could theoritically, but not practically. -- 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
