Sounds like my original idea has no chance of working. But maybe Scott's idea for resource groups at the SC period level has a better chance ?
On Wed, 19 Jun 2019 at 16:48, Tom Marchant < 0000000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote: > On Wed, 19 Jun 2019 10:55:13 +0300, Mike Shorkend wrote: > > >How about submitting a requirement to IBM that would add a control to WLM > >This control would re-classify a ZIIP eligible workload to a different > >service class if it spills over to a GCP because you are running your > ZIIPS > >hot (or hit the "generosity factor" for DB2 work). This service class > could > >have a lower importance/goal than the original service class. You could > >also restrict its CPU consumption using a resource group. > > > >In other words, have a workload run at high priority on ZIIP, but limit it > >if it crosses over to GCP. > > I think you are suggesting that any task that is part of such a workload > be > (potentially) reclassified every time it is selected for dispatch. If > selected for > dispatch on a ZIIP, it would go to the original service class. If selected > to be > dispatched on a GP it would be reclassified to the pther service class. > > What do you think should happen if the address space has multiple tasks > and some are running on ZIIP and some are running on GP? > > -- > Tom Marchant > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike Shorkend m...@shorkend.com www.shorkend.com Tel: +972524208743 Fax: +97239772196 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN