>If this is a production LPAR and all the DDF work coming in is production, >classify it as such.
I can tell you what we did. 1. Set up a high velocity service class with an importance just below production online (IMS, CICS, etcf). 2. Set up a transaction class with two periods: a. The first was set up to consume the equivalent of 0.1 seconds of CPU, and had a response goal of 90% < 0.5 seconds. This figure is site dependent. b. The second was set up with an importance just lower than P1. 3. Set up many report classes for each id. We classified by id, because each id was attributable to an application. 4. Turn off the SQL governor -- they're just going to resubmit when a transaction abends. 5. Assign the high (business) priority work to number 1. 6. Assign the other work to #2. 7. Monitor. Analyse. Tune. Rinse. Repeat. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
