If you recently created a service class for your HOTBATCH see if the CICS
SOS issue started around the same time. Depending on how this is setup vs.
the CICS service class this might have caused the problem. You want to make
sure that the HOTBATCH cannot steal cycles from the CICS.
Joel Wolpert
Performance and Capacity Planning consultant
WEBSITE: www.perfconsultant.com
----- Original Message -----
From: "gsg" <gsg_...@yahoo.com>
Newsgroups: bit.listserv.ibm-main
To: <IBM-MAIN@bama.ua.edu>
Sent: Tuesday, August 18, 2009 7:53 PM
Subject: Re: LPAR strictly for CICS Onlines
No knowing any better is probably me best anwer. I thought we would be
able to control resources better. However, using the CPU Critical may be
an
option also. However, I think that we created a service class recently
for our
HOTBATCH service class. I don't think we would want to many service
classes running as CPU critical.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
