Yes, some of the descriptions leave a little bit to be desired. I like to try to stay away from capping unless absolutely necessary but do have some. Maybe there was an entry in the notes file in WLM stating why that Service Class was resource capped? I try to keep up with documentation, even for myself, as I find going back I'm asking myself sometimes why I did what I did. I have Mainview, what was the screen name that you saw this in?
--- On Tue, 9/22/09, McKown, John <john.mck...@healthmarkets.com> wrote: From: McKown, John <john.mck...@healthmarkets.com> Subject: Re: WLM question - delayed due to CPUCAPPED To: IBM-MAIN@bama.ua.edu Date: Tuesday, September 22, 2009, 7:09 PM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Patrick Falcone > Sent: Tuesday, September 22, 2009 1:20 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: WLM question - delayed due to CPUCAPPED > > Hmmm, you're probably right. > > John, go to the field descriptor and hit PF1 and you should > get the description for the field. > Unfortunately, I didn't understand the description. However I did find out that the storage class does indeed have an associated resource group. So that is likely what the capping is referring to. I have no idea why we did this. And we just removed it. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . (817)-961-6183 cell john.mck...@healthmarkets.com . www.HealthMarkets.com ---------------------------------------------------------------------- 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
