Thanks. That helps. However, doesn't that now suggest that the monitor's display is actually wrong? In other words, I would expect that if a monitor was going to display a dispatching priority, it would also display the service class with which it was associated. It would be erroneous to report on a service class and include a dispatching priority from a unit of work that was running in a different service class.
I would expect more consistency than that. Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Martin Packer Sent: Thursday, April 5, 2018 11:30 AM To: [email protected] Subject: Re: WLM and Dispatching Priority A DB2 WLM Stored Procedures server address space might well show up as being in a service class. However, it - with its peers - supports a Service Class / Application Environment combination with a queue of work. The queue of work is EXCLUSIVELY that with the Service Class and also the Application Environment stated. The work executes at that Service Class' goal, not the server address space's Service Class goal. (I wrote the Server Address Space Management chapters in the 2003/4 Redbook "DB2 Stored Procedures: Through The Call And Beyond" - and did quite a bit of research and client work in this very area.) Cheers, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM +44-7802-245-584 email: [email protected] Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker Podcast Series (With Marna Walle): https://developer.ibm.com/tv/mpt/ or https://itunes.apple.com/gb/podcast/mainframe-performance-topics/id112794357 3?mt=2 Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: Gerhard Adam <[email protected]> To: [email protected] Date: 05/04/2018 18:49 Subject: Re: WLM and Dispatching Priority Sent by: IBM Mainframe Discussion List <[email protected]> I don't understand what you're trying to say. Enclaves are certainly assigned to service classes and can be reset or even quiesced. From the ENC display in SDSF NAME SSType Status SrvClass Per 2400000002 STC INACTIVE SYSSTC 1 4C0000000C STC ACTIVE SRVHIM 1 7000000015 STC INACTIVE SRVHIM 1 3800000007 STC ACTIVE SRVHIM 1 480000000B STC INACTIVE SRVHIM 1 500000000D STC ACTIVE SRVHIM 1 6800000013 STC INACTIVE SRVHIM 1 3400000006 STC ACTIVE SRVHIM 1 440000000A STC INACTIVE SRVHIM 1 6000000011 STC ACTIVE SRVHIM 1 6400000012 STC INACTIVE SRVHIM 1 4000000009 STC ACTIVE SRVHIM 1 580000000F STC INACTIVE SRVHIM 1 5C00000010 STC ACTIVE SRVHIM 1 6C00000014 STC INACTIVE SRVHIM 1 3C00000008 STC ACTIVE SRVHIM 1 540000000E STC INACTIVE SRVHIM 1 I specifically don't understand what you mean by service classes not being applicable to server address spaces. How can any address space that is associated with a service class, not be managed to that service class' goals? It would have to be identifiable as a separate internal service class, but whatever the reason, it would have to be something that can be specifically seen and tracked using the Type 99 data. Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Marchant Sent: Thursday, April 5, 2018 9:35 AM To: [email protected] Subject: Re: WLM and Dispatching Priority On Thu, 5 Apr 2018 08:37:20 -0700, Gerhard Adam wrote: >I don't see the relevance of enclaves or anything else in this. It is >the service class period that matters. That is only one factor. Transaction response time goals are another factor. > >So, if I assigned DB2, enclaves, TSO, and batch to the same service >class, You don't assign an enclave to a service class. WLM defines enclaves based upon transaction response time goals and the address spaces that are involved in those transactions. Those server address spaces are managed to meet the goals of the transactions that include that address space in their enclave(s). This can get complicated because many different transactions with different requirements and involving different address spaces can be in different enclaves that involve an address space. WLM does not change the service class of those server address spaces, but it no longer manages them based on their service class. It wouldn't make any sense to change the service class of the DB2 region to match the service class of a CICS transaction whose enclave requires the DP of the DB2 region to change. At least, that's the way I understand it. >they should still all have the same dispatching priority. Workload >Manager doesn't care what type of work is in the service class, since >only the data related to the service class can be examined. That's not true of server address spaces. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
