I think that's the rub. How much can you afford in discretionary, if any. I played with disc. early on and found that since I different requirements for production batch workloads based on time zone and importance, and there was very little if any cycles left for test, I had to end up putting the test batch into a low importance service class where it would at least get some service over time. And like Ted I've worked for insurance companies who are mostly reluctant to get upgrades until absolutely necessary.
I think you mention this. How many cycles are left after system support and program product tasks, production online and priority production batch are accounted for? If it becomes problematic to run disc., based on wait for CPU, you're left with a low importance service class for your test workloads. Mark Zelden <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <[email protected]> 10/10/2006 05:47 PM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: Another BIG Mainframe Bites the Dust Perhaps there was not enough discretionary work defined. Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsuti ---------------------------------------------------------------------- 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
