On Mon, 7 May 2012 09:20:56 -0700, Norman Hollander on DesertWiz <[email protected]> wrote:
>While I would agree with DDF being most like TSO, many sites have challenges >enforcing DDF work. Either they can't tell what kind of work it is, or they >can't >really tell if it is important. Sometimes. But one can get a clue via RMF III. At least for the long running enclaves. >To compensate for that, sites add the 3rd >period to >prevent misbehaving DDF work from consuming their systems. They often treat >3rd period DDF as Batch-like work. Yes, I do that - but for development / test only. I have several DDF SCs. A "DDFHI" SC that only has 2 periods with the 1st period one of only a few IMP=1 SC periods in the environment. What falls into here are enclaves generated from WebSphere, which I know are interactive transactions. This is the "loved one" application. Period 2 still has a fairly aggressive velocity goal and IMP=2. My normal production DDF class has 2 periods - the 2nd period has a goal similar to batch. My devl/test DDF class is the only one that has 3 periods. The 2nd period has a long duration (200000) and a low importance, but is still better than test batch, which is discretionary. The 3rd period is discretionary. I forgot how long in wall clock time 200000 was when I set this up (10-15 seconds on a system with avail. cycles), but I figured anything longer than that was more like batch than interactive. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
