Re: WLM and Dispatching Priority
Likewise SMF 30. Cheers, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com 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/id1127943573?mt=2 Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: Tom Marchant <000a2a8c2020-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Date: 06/04/2018 16:10 Subject: Re: WLM and Dispatching Priority Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Fri, 6 Apr 2018 06:05:03 -0700, Gerhard Adam wrote: >If we display the address space, then only the address space service class >and dispatching priority should be shown. If those are different, then it >suggests a problem with the display. The display should also indicate whether WLM considers the address space to be server address space. If it is, it is not managed by service class, but to meet the goals defined for the work that the server is processing. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
On Fri, 6 Apr 2018 06:05:03 -0700, Gerhard Adam wrote: >If we display the address space, then only the address space service class >and dispatching priority should be shown. If those are different, then it >suggests a problem with the display. The display should also indicate whether WLM considers the address space to be server address space. If it is, it is not managed by service class, but to meet the goals defined for the work that the server is processing. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Agreed. That's not a problem and with multiple service classes, one would expect multiple dispatching priorities to be assigned to the enclaves. However, that suggests that when the address space is displayed, such considerations shouldn't matter. We aren't displaying the enclave or any other unit of work. If we display the address space, then only the address space service class and dispatching priority should be shown. If those are different, then it suggests a problem with the display. Adam -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gabriel Tully Sent: Friday, April 6, 2018 4:51 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority But the address space can be servicing multiple enclaves with different service classes. Granted that the DP is generally adjusted to the highest goal, but it's a moving target that would lead to inaccuracies. Thanks, Gabe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Right, enclaves are independent units of work (running under pre-emptible SRBs), running with their own DP's, not the DP of the owning address space. Kees. Grtn, Kees. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Gabriel Tully > Sent: 06 April, 2018 13:57 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > Sorry, I spoke to soon. I believe a new application environment address > space is created to serve different service classes. > > Thanks, > Gabe > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Sorry, I spoke to soon. I believe a new application environment address space is created to serve different service classes. Thanks, Gabe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
But the address space can be servicing multiple enclaves with different service classes. Granted that the DP is generally adjusted to the highest goal, but it's a moving target that would lead to inaccuracies. Thanks, Gabe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Martin Packer Sent: Thursday, April 5, 2018 11:30 AM To: IBM-MAIN@LISTSERV.UA.EDU 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: martin_pac...@uk.ibm.com 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 <gada...@charter.net> To: IBM-MAIN@LISTSERV.UA.EDU Date: 05/04/2018 18:49 Subject:Re: WLM and Dispatching Priority Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> 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 NAMESSType StatusSrvClass Per 240002 STCINACTIVE SYSSTC 1 4C000C STCACTIVE SRVHIM 1 700015 STCINACTIVE SRVHIM 1 380007 STCACTIVE SRVHIM 1 48000B STCINACTIVE SRVHIM 1 5D STCACTIVE SRVHIM 1 680013 STCINACTIVE SRVHIM 1 340006 STCACTIVE SRVHIM 1 44000A STCINACTIVE SRVHIM 1 600011 STCACTIVE SRVHIM 1 640012 STCINACTIVE SRVHIM 1 49 STCACTIVE SRVHIM 1 58000F STCINACTIVE SRVHIM 1 5C0010 STCACTIVE SRVHIM 1 6C0014 STCINACTIVE SRVHIM 1 3C0008 STCACTIVE SRVHIM 1 54000E STCINACTIVE 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Thursday, April 5, 2018 9:35 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 dispatchin
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: martin_pac...@uk.ibm.com 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/id1127943573?mt=2 Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: Gerhard Adam <gada...@charter.net> To: IBM-MAIN@LISTSERV.UA.EDU Date: 05/04/2018 18:49 Subject:Re: WLM and Dispatching Priority Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> 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 NAMESSType StatusSrvClass Per 240002 STCINACTIVE SYSSTC 1 4C000C STCACTIVE SRVHIM 1 700015 STCINACTIVE SRVHIM 1 380007 STCACTIVE SRVHIM 1 48000B STCINACTIVE SRVHIM 1 5D STCACTIVE SRVHIM 1 680013 STCINACTIVE SRVHIM 1 340006 STCACTIVE SRVHIM 1 44000A STCINACTIVE SRVHIM 1 600011 STCACTIVE SRVHIM 1 640012 STCINACTIVE SRVHIM 1 49 STCACTIVE SRVHIM 1 58000F STCINACTIVE SRVHIM 1 5C0010 STCACTIVE SRVHIM 1 6C0014 STCINACTIVE SRVHIM 1 3C0008 STCACTIVE SRVHIM 1 54000E STCINACTIVE 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Thursday, April 5, 2018 9:35 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless stated otherwise above: IBM United
Re: WLM and Dispatching Priority
My dispute about the dispatching priorities comes from the Type 99 subtype 1 records.I've included the data from a report that shows that the dispatching priority changes [including the projected changes afterwards] are all based on the entire service class. In this case, it clearly shows that WLM is making the assessment and increasing the receiver's dispatching priority. You can see how WLM took the initial value at dispatching priority 247 and combined that with 251 to arrive at the new projected value. Whether SRM is the specific mechanism that makes that change isn't important here. 167 233 ONLTST 1 1.00 1.27 270 PA - Receiver candidate selected 167 233 SERVERS 1 11.66 2.59 308 PA - Donor period 167 233 SERVERS 1 11.66 2.59 880 PA - Processor donor selected 167 233 ONLTST 1 1.00 1.27 620 PA - Assess moving receiver up to occupied priority 167 233 ONLTST 1.96 1.25 750 PA - Increase receiver priority 167 233 SERVERS 1 14.00 2.59 940 PA - Unchanged donor Priority Table Report: Numbers as indicated are "at priority" DP AfterUtilizationCPU Samples Wait to Cumulative Utilization Avg MTTW (SU/sec) Used (SU/sec) PA Unbunching Init Proj Using Delay Using Ratio Init Projected Achievable Initial Projected Actual Projected --- 19220.7% 20.7% 6 25 4 134.3% 134.3% .0% 3.6 3.6 8302.1 8302.1 231 3.2%3.2% 0 1 1 113.6% 113.6% .0% 4.0 4.0 258.1258.1 23361.8% 61.8% 45 24 1 110.4% 110.4% .0% 12.7 12.7 5930.0 5930.0 235 .8% .8% 0 0 1 48.6% 48.6% .0% 6.3 6.30.8 0.8 23712.0% 12.0% 4 2 1 47.8% 47.8% .0% 3.1 3.1 3838.9 3838.9 239 3.9%3.9% 4 4 1 35.8% 35.8% .0% 3.1 3.1 2010.5 2010.5 243 .6% .6% 0 0 1 31.9% 31.9% .0% 3.2 3.2 16.0 16.0 245 .6% .6% 1 0 1 31.3% 31.3% .0% 2.6 2.6 359.4359.4 247 7.0% .0% 4 5 1 30.7% 30.7% 30.7% 2.7 6.3 2910.4 0.0 251 3.8% 10.8% 11 2 0 23.7% 30.7% 30.7% 12.7 6.7 2013.0 4923.4 253 .1% .1% 0 0 0 19.9% 19.9% 19.9% 9.2 9.23.0 3.0 25410.5% 10.5% 13 1 0 19.8% 19.8% .0% 3.0 3.0 4974.4 4974.4 255 9.3%9.3% 8 0 0 9.3% 9.3% .0% 1.8 1.8 4215.4 4215.4 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Thursday, April 5, 2018 9:09 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority SRM is a component of the system control program. It determines which address spaces, of all active address spaces, should be given access to system resources and the rate at which each address space is allowed to consume these resources. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Thursday, April 05, 2018 12:06 PM To: IBM-MAIN@LISTSERV.UA.EDU <mailto:IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: WLM and Dispatching Priority https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieaw200/iea3w201112.htm Dispatching Priority SRM defines dispatching priority for service class periods. All address spaces in a service class period have the same base dispatching priority. Multiple service class periods may have the same base dispatching priority. After a dispatching priority change, service class periods may be remapped to different dispatching priorities such that there is an unoccupied priority between each occupied priority. This process is referred to as priority unbunching. The dispatching priority is recorded in the subtype 2 records. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Thursday, April 05, 2018 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU <mailto:IBM-MAIN@LISTSERV.UA.EDU> Subject: Re: WLM and Dispatching Priority I beg to differ, but do
Re: WLM and Dispatching Priority
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 NAMESSType StatusSrvClass Per 240002 STCINACTIVE SYSSTC 1 4C000C STCACTIVE SRVHIM 1 700015 STCINACTIVE SRVHIM 1 380007 STCACTIVE SRVHIM 1 48000B STCINACTIVE SRVHIM 1 5D STCACTIVE SRVHIM 1 680013 STCINACTIVE SRVHIM 1 340006 STCACTIVE SRVHIM 1 44000A STCINACTIVE SRVHIM 1 600011 STCACTIVE SRVHIM 1 640012 STCINACTIVE SRVHIM 1 49 STCACTIVE SRVHIM 1 58000F STCINACTIVE SRVHIM 1 5C0010 STCACTIVE SRVHIM 1 6C0014 STCINACTIVE SRVHIM 1 3C0008 STCACTIVE SRVHIM 1 54000E STCINACTIVE 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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Marchant Sent: Thursday, April 5, 2018 9:35 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Your documentation doesn't say what you say it does. It explicitly indicates that service class periods are associated with a dispatching priority and does not say anything about differences within a service class. In short, there is nothing to indicate that individual address spaces would be subject to variations in dispatching priorities within a service class period. Adam -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Thursday, April 5, 2018 9:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieaw200/iea3w201112.htm Dispatching Priority SRM defines dispatching priority for service class periods. All address spaces in a service class period have the same base dispatching priority. Multiple service class periods may have the same base dispatching priority. After a dispatching priority change, service class periods may be remapped to different dispatching priorities such that there is an unoccupied priority between each occupied priority. This process is referred to as priority unbunching. The dispatching priority is recorded in the subtype 2 records. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Thursday, April 05, 2018 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority I beg to differ, but do you have documentation that supports what you say? I have looked at a lot of type 99 records and WLM most certainly assigns the DP. Sent from my iPhone > On Apr 5, 2018, at 8:44 AM, Edgington, Jerry <jerry.edging...@westernsouthernlife.com> wrote: > > WLM uses the configuration to determine what SRVCLASS a specific piece of work should be assigned upon initial job entry. After that, WLM will recommend to SRM how to adjust the dispatching priorities, based on information provided in WLM definitions. > > WLM doesn't make changes to dispatching priorities, only SRM does that. Also, SRVCLASS doesn't equal a specific dispatching priority. > > SRM still works like it always has and WLM is way of defining "business rules" to workload versus assigning specific dispatching priorities to the workload. > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gerhard Adam > Sent: Thursday, April 05, 2018 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > I don't see the relevance of enclaves or anything else in this. It is the service class period that matters. > > So, if I assigned DB2, enclaves, TSO, and batch to the same service class, 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. > > I would expect to see different dispatching priorities for the small consumer, or an address space that has been temporarily promoted, but that should only be short-term. I would also expect to see different dispatching priorities for the MTTW usage in discretionary. > > However, I still don't see how a goal-managed service class period can have different dispatching priorities. It would render the goal meaningless. > > Adam > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Martin Packer > Sent: Thursday, April 5, 2018 7:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > There is also DIST and DBM1 in there. The action will be heavily > geared towards DBM1. (DIST has work in it mostly on Independent > Enclaves so relatively little of the work therein is at the address > space's DP.) > > Cheers, Martin > > Martin Packer > > zChampion, Systems Investigator & Performance Troubleshooter, IBM > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu
Re: WLM and Dispatching Priority
SRM is a component of the system control program. It determines which address spaces, of all active address spaces, should be given access to system resources and the rate at which each address space is allowed to consume these resources. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edgington, Jerry Sent: Thursday, April 05, 2018 12:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaw200/iea3w201112.htm Dispatching Priority SRM defines dispatching priority for service class periods. All address spaces in a service class period have the same base dispatching priority. Multiple service class periods may have the same base dispatching priority. After a dispatching priority change, service class periods may be remapped to different dispatching priorities such that there is an unoccupied priority between each occupied priority. This process is referred to as priority unbunching. The dispatching priority is recorded in the subtype 2 records. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Thursday, April 05, 2018 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority I beg to differ, but do you have documentation that supports what you say? I have looked at a lot of type 99 records and WLM most certainly assigns the DP. Sent from my iPhone > On Apr 5, 2018, at 8:44 AM, Edgington, Jerry > <jerry.edging...@westernsouthernlife.com> wrote: > > WLM uses the configuration to determine what SRVCLASS a specific piece of > work should be assigned upon initial job entry. After that, WLM will > recommend to SRM how to adjust the dispatching priorities, based on > information provided in WLM definitions. > > WLM doesn't make changes to dispatching priorities, only SRM does that. > Also, SRVCLASS doesn't equal a specific dispatching priority. > > SRM still works like it always has and WLM is way of defining "business > rules" to workload versus assigning specific dispatching priorities to the > workload. > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gerhard Adam > Sent: Thursday, April 05, 2018 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > I don't see the relevance of enclaves or anything else in this. It is the > service class period that matters. > > So, if I assigned DB2, enclaves, TSO, and batch to the same service class, > 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. > > I would expect to see different dispatching priorities for the small > consumer, or an address space that has been temporarily promoted, but that > should only be short-term. I would also expect to see different dispatching > priorities for the MTTW usage in discretionary. > > However, I still don't see how a goal-managed service class period can have > different dispatching priorities. It would render the goal meaningless. > > Adam > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Martin Packer > Sent: Thursday, April 5, 2018 7:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > There is also DIST and DBM1 in there. The action will be heavily > geared towards DBM1. (DIST has work in it mostly on Independent > Enclaves so relatively little of the work therein is at the address > space's DP.) > > Cheers, Martin > > Martin Packer > > zChampion, Systems Investigator & Performance Troubleshooter, IBM > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaw200/iea3w201112.htm Dispatching Priority SRM defines dispatching priority for service class periods. All address spaces in a service class period have the same base dispatching priority. Multiple service class periods may have the same base dispatching priority. After a dispatching priority change, service class periods may be remapped to different dispatching priorities such that there is an unoccupied priority between each occupied priority. This process is referred to as priority unbunching. The dispatching priority is recorded in the subtype 2 records. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Thursday, April 05, 2018 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority I beg to differ, but do you have documentation that supports what you say? I have looked at a lot of type 99 records and WLM most certainly assigns the DP. Sent from my iPhone > On Apr 5, 2018, at 8:44 AM, Edgington, Jerry > <jerry.edging...@westernsouthernlife.com> wrote: > > WLM uses the configuration to determine what SRVCLASS a specific piece of > work should be assigned upon initial job entry. After that, WLM will > recommend to SRM how to adjust the dispatching priorities, based on > information provided in WLM definitions. > > WLM doesn't make changes to dispatching priorities, only SRM does that. > Also, SRVCLASS doesn't equal a specific dispatching priority. > > SRM still works like it always has and WLM is way of defining "business > rules" to workload versus assigning specific dispatching priorities to the > workload. > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gerhard Adam > Sent: Thursday, April 05, 2018 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > I don't see the relevance of enclaves or anything else in this. It is the > service class period that matters. > > So, if I assigned DB2, enclaves, TSO, and batch to the same service class, > 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. > > I would expect to see different dispatching priorities for the small > consumer, or an address space that has been temporarily promoted, but that > should only be short-term. I would also expect to see different dispatching > priorities for the MTTW usage in discretionary. > > However, I still don't see how a goal-managed service class period can have > different dispatching priorities. It would render the goal meaningless. > > Adam > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Martin Packer > Sent: Thursday, April 5, 2018 7:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > There is also DIST and DBM1 in there. The action will be heavily > geared towards DBM1. (DIST has work in it mostly on Independent > Enclaves so relatively little of the work therein is at the address > space's DP.) > > Cheers, Martin > > Martin Packer > > zChampion, Systems Investigator & Performance Troubleshooter, IBM > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
I beg to differ, but do you have documentation that supports what you say? I have looked at a lot of type 99 records and WLM most certainly assigns the DP. Sent from my iPhone > On Apr 5, 2018, at 8:44 AM, Edgington, Jerry > <jerry.edging...@westernsouthernlife.com> wrote: > > WLM uses the configuration to determine what SRVCLASS a specific piece of > work should be assigned upon initial job entry. After that, WLM will > recommend to SRM how to adjust the dispatching priorities, based on > information provided in WLM definitions. > > WLM doesn't make changes to dispatching priorities, only SRM does that. > Also, SRVCLASS doesn't equal a specific dispatching priority. > > SRM still works like it always has and WLM is way of defining "business > rules" to workload versus assigning specific dispatching priorities to the > workload. > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Gerhard Adam > Sent: Thursday, April 05, 2018 11:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > I don't see the relevance of enclaves or anything else in this. It is the > service class period that matters. > > So, if I assigned DB2, enclaves, TSO, and batch to the same service class, > 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. > > I would expect to see different dispatching priorities for the small > consumer, or an address space that has been temporarily promoted, but that > should only be short-term. I would also expect to see different dispatching > priorities for the MTTW usage in discretionary. > > However, I still don't see how a goal-managed service class period can have > different dispatching priorities. It would render the goal meaningless. > > Adam > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Martin Packer > Sent: Thursday, April 5, 2018 7:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > There is also DIST and DBM1 in there. The action will be heavily geared > towards DBM1. (DIST has work in it mostly on Independent Enclaves so > relatively little of the work therein is at the address space's DP.) > > Cheers, Martin > > Martin Packer > > zChampion, Systems Investigator & Performance Troubleshooter, IBM > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
WLM uses the configuration to determine what SRVCLASS a specific piece of work should be assigned upon initial job entry. After that, WLM will recommend to SRM how to adjust the dispatching priorities, based on information provided in WLM definitions. WLM doesn't make changes to dispatching priorities, only SRM does that. Also, SRVCLASS doesn't equal a specific dispatching priority. SRM still works like it always has and WLM is way of defining "business rules" to workload versus assigning specific dispatching priorities to the workload. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Thursday, April 05, 2018 11:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority I don't see the relevance of enclaves or anything else in this. It is the service class period that matters. So, if I assigned DB2, enclaves, TSO, and batch to the same service class, 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. I would expect to see different dispatching priorities for the small consumer, or an address space that has been temporarily promoted, but that should only be short-term. I would also expect to see different dispatching priorities for the MTTW usage in discretionary. However, I still don't see how a goal-managed service class period can have different dispatching priorities. It would render the goal meaningless. Adam -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Martin Packer Sent: Thursday, April 5, 2018 7:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority There is also DIST and DBM1 in there. The action will be heavily geared towards DBM1. (DIST has work in it mostly on Independent Enclaves so relatively little of the work therein is at the address space's DP.) Cheers, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
I don't see the relevance of enclaves or anything else in this. It is the service class period that matters. So, if I assigned DB2, enclaves, TSO, and batch to the same service class, 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. I would expect to see different dispatching priorities for the small consumer, or an address space that has been temporarily promoted, but that should only be short-term. I would also expect to see different dispatching priorities for the MTTW usage in discretionary. However, I still don't see how a goal-managed service class period can have different dispatching priorities. It would render the goal meaningless. Adam -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Martin Packer Sent: Thursday, April 5, 2018 7:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority There is also DIST and DBM1 in there. The action will be heavily geared towards DBM1. (DIST has work in it mostly on Independent Enclaves so relatively little of the work therein is at the address space's DP.) Cheers, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
While multiple periods certainly makes sense, the idea that different dispatching priorities exist within a single period service class doesn't. Workload manager adjusts the dispatching priority of an entire service class, both in terms of "unbunching" and in the algorithms used to assess the goals. To have individual units of work within a service class have different dispatching priorities renders any measurement meaningless. In other words, a service class could be meeting its goals simply because one unit of work has a higher priority while everything else suffers. Whether it is an enclave or an application's environment, presumably they would be classified into a unique service class in order to have a different dispatching priority. Adam -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: Thursday, April 5, 2018 6:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: WLM and Dispatching Priority Correct. Kees. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gabriel Tully > Sent: 05 April, 2018 15:29 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > These address spaces look like stored procedure address spaces and > they are likely marked as a server . Their goals would be managed > under the DDF subsystem in WLM classification rules and would depend > on what srvclasses are this ASID is servicing. > > Gabe > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
There is also DIST and DBM1 in there. The action will be heavily geared towards DBM1. (DIST has work in it mostly on Independent Enclaves so relatively little of the work therein is at the address space's DP.) Cheers, Martin Martin Packer zChampion, Systems Investigator & Performance Troubleshooter, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com 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/id1127943573?mt=2 Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA From: Gabriel Tully <gjtu...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 05/04/2018 14:29 Subject: Re: WLM and Dispatching Priority Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> These address spaces look like stored procedure address spaces and they are likely marked as a server . Their goals would be managed under the DDF subsystem in WLM classification rules and would depend on what srvclasses are this ASID is servicing. Gabe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
On Thu, 5 Apr 2018 13:37:43 +, Edgington, Jerry wrote: >Dispatching priorities work the same way prior to WLM. If Service class is >WLM velocity, then the dispatching priority is a range, just like prior to >WLM. >However, I don't remember which way SRM adjusts the DP. SRM would >adjust DP up/down depending upon the resource, I/O or CPU, being consumed >within the range. > >For example; >- DP C0-CF, SRM would adjust the dispatching priority up or down, if the > process is using more I/O versus CPU. This sounds like the SRM Mean Time To Wait algorithm. AFAIK, WLM only does that for discretionary work. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Here is my understanding of WLM and dispatching priorities.
Dispatching priorities work the same way prior to WLM. If Service class is WLM
velocity, then the dispatching priority is a range, just like prior to WLM.
However, I don't remember which way SRM adjusts the DP. SRM would adjust DP
up/down depending upon the resource, I/O or CPU, being consumed within the
range.
For example;
- DP C0-CF, SRM would adjust the dispatching priority up or down, if the
process is using more I/O versus CPU.
- I believe SRM would move closer to CF, if I/O intensive and closer to
C0 if CPU intensive, but it could be the reverse
WLM only adjusts which dispatching priority range, if velocity.
Jerry
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gerhard Adam
Sent: Thursday, April 05, 2018 7:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WLM and Dispatching Priority
Has anyone ever seen something like this before? Two started tasks {both
DB2 address spaces] in the same service class and yet have different
dispatching priorities? This screen capture shows the essential details.
Any thoughts?
Adam
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Correct. Kees. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Gabriel Tully > Sent: 05 April, 2018 15:29 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: WLM and Dispatching Priority > > These address spaces look like stored procedure address spaces and they > are likely marked as a server . Their goals would be managed under the > DDF subsystem in WLM classification rules and would depend on what > srvclasses are this ASID is servicing. > > Gabe > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
These address spaces look like stored procedure address spaces and they are likely marked as a server . Their goals would be managed under the DDF subsystem in WLM classification rules and would depend on what srvclasses are this ASID is servicing. Gabe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Depends on the meaning of 'manage'.
Individual units of work don't have a goal, but realizing a Service Class's
Goal can only be done by managing the attributes of the individual tasks in the
Service Class.
As to the suggestion of Service Class Periods: the DB2 Service Classes have
only 1 Period.
Grtn,
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Gerhard Adam
> Sent: 05 April, 2018 15:15
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WLM and Dispatching Priority
>
> Workload manager doesn't manage individual address spaces within a
> service class. That wouldn't make any sense.
>
> That's why my question. After all, if the service class has varying
> dispatching priorities, then how can the goal of the service class be
> assessed when individual units of work have different goals?
>
> Adam
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Thursday, April 5, 2018 6:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WLM and Dispatching Priority
>
> Why shouldn't they? WLM manages Goals and uses all resources, including
> DPTRY, to realize them.
> I see this now:
>
> Jobname SrvClass CUR
> PTY
> MZCMT01A BAT_PJ220
> COECM01L BAT_PJ224
> MZFFB03B BAT_PJ214
> DBP1DBM1 DB2P_CTL 246
> DBP1DIST DB2P_CTL 246
> DB2PSPU1 DB2P_CTL 242
> DB2PSPS2 DB2P_CTL 255
> DBH1DBM1 DB2P_CTL 246
> DBK1DIST DB2P_CTL 246
> DBK1DBM1 DB2P_CTL 246
> DBH1DIST DB2P_CTL 246
>
> Kees.
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Gerhard Adam
> > Sent: 05 April, 2018 13:23
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: WLM and Dispatching Priority
> >
> > Has anyone ever seen something like this before? Two started tasks
> > {both
> > DB2 address spaces] in the same service class and yet have different
> > dispatching priorities? This screen capture shows the essential
> > details.
> >
> > Any thoughts?
> >
> >
> >
> >
> >
> > Adam
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail
> or any attachment may be disclosed, copied or distributed, and that any
> other action related to this e-mail or attachment is strictly
> prohibited, and may be unlawful. If you have received this e-mail by
> error, please notify the sender immediately by return e-mail, and delete
> this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
> its employees shall not be liable for the incorrect or incomplete
> transmission of this e-mail or any attachments, nor responsible for any
> delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatsch
Re: WLM and Dispatching Priority
On Thu, 5 Apr 2018 06:14:49 -0700, Gerhard Adam wrote: >Workload manager doesn't manage individual address spaces within >a service class. That wouldn't make any sense. > >That's why my question. After all, if the service class has varying >dispatching priorities, then how can the goal of the service class be >assessed when individual units of work have different goals? Are these DB2 regions part of an enclave that is managed by response time goals, perhaps for CICS or IMS? In that case, IIRC, the service class assigned is used only for startup. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
DB2 DOESN'T alter DPs. So far I see no cause to panic - so long as goals
are being met. (And that they are the right goals.)
Cheers, Martin
Martin Packer
zChampion, Systems Investigator & Performance Troubleshooter, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
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/id1127943573?mt=2
Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA
From: Allan Staller <allan.stal...@hcl.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 05/04/2018 14:09
Subject: Re: WLM and Dispatching Priority
Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Possible bug in reporting tool? (SDSF, RMF, 3rd Party).
Never heard of this, however, if WLM CICS Transaction Management is
involved, I can see where it might happen.
Also, DB2 is smart enough to alter DP's if it thinks it needs to.
I would ask IBM for an explanation.
Hopefully you are recording SMF99's and relevant DB2 information.
HTH,
Has anyone ever seen something like this before? Two started tasks {both
DB2 address spaces] in the same service class and yet have different
dispatching priorities? This screen capture shows the essential details.
Any thoughts?
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only. E-mail transmission is not
guaranteed to be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or may contain
viruses in transmission. The e mail and its contents (with or without
referred errors) shall therefore not attach any liability on the
originator or HCL or its affiliates. Views or opinions, if any, presented
in this email are solely those of the author and may not necessarily
reflect the views or opinions of HCL or its affiliates. Any form of
reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior
written consent of authorized representative of HCL is strictly
prohibited. If you have received this email in error please delete it and
notify the sender immediately. Before opening any email and/or
attachments, please check them for viruses and other defects.
--
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Workload manager doesn't manage individual address spaces within a service
class. That wouldn't make any sense.
That's why my question. After all, if the service class has varying
dispatching priorities, then how can the goal of the service class be assessed
when individual units of work have different goals?
Adam
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Thursday, April 5, 2018 6:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WLM and Dispatching Priority
Why shouldn't they? WLM manages Goals and uses all resources, including DPTRY,
to realize them.
I see this now:
Jobname SrvClass CUR
PTY
MZCMT01A BAT_PJ220
COECM01L BAT_PJ224
MZFFB03B BAT_PJ214
DBP1DBM1 DB2P_CTL 246
DBP1DIST DB2P_CTL 246
DB2PSPU1 DB2P_CTL 242
DB2PSPS2 DB2P_CTL 255
DBH1DBM1 DB2P_CTL 246
DBK1DIST DB2P_CTL 246
DBK1DBM1 DB2P_CTL 246
DBH1DIST DB2P_CTL 246
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Gerhard Adam
> Sent: 05 April, 2018 13:23
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WLM and Dispatching Priority
>
> Has anyone ever seen something like this before? Two started tasks
> {both
> DB2 address spaces] in the same service class and yet have different
> dispatching priorities? This screen capture shows the essential
> details.
>
> Any thoughts?
>
>
>
>
>
> Adam
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Yes, sorry. For some reason the paste didn't work.
Basically it simply shows two tasks in the same service class with different
dispatching priorities. One has a priority of F6 and the other is F0.
Adam
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Elardus Engelbrecht
Sent: Thursday, April 5, 2018 5:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: WLM and Dispatching Priority
Gerhard Adam wrote:
>Has anyone ever seen something like this before? Two started tasks {both DB2
>address spaces] in the same service class and yet have different dispatching
>priorities? This screen capture shows the essential details.
What screen print? I only see white letters on a white background... ;-D
Perhaps you should re-post your question with more details using some
copy/paste actions?
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Agreed, and further to that point...
... Does the WLM Policy include Using / Delay for I/O samples?
In my extensive experience if so
1) The Velocity achieved is normally very high. (Indicates a protective
goal of 70% or higher, generally. Imp 1 BTW.)
2) The samples are dominated by Using I/O.
So probably the CPU component - hence DP - is "almost random". (Don't
shoot me for the rhetorical and inaccurate flourish.) :-)
Some people might benefit from / enjoy / snigger at / curse at THIS:
https://www.youtube.com/watch?v=UMtjB_GUyxs . It's a relevant YouTube
screencast of mine "Screencast 12 - Get WLM Set Up Right For DB2".
Cheers, Martin
Martin Packer
zChampion, Systems Investigator & Performance Troubleshooter, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
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/id1127943573?mt=2
Youtube channel: https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA
From: "Vernooij, Kees (ITOPT1) - KLM" <kees.verno...@klm.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 05/04/2018 14:02
Subject:Re: WLM and Dispatching Priority
Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU>
Why shouldn't they? WLM manages Goals and uses all resources, including
DPTRY, to realize them.
I see this now:
Jobname SrvClass CUR
PTY
MZCMT01A BAT_PJ220
COECM01L BAT_PJ224
MZFFB03B BAT_PJ214
DBP1DBM1 DB2P_CTL 246
DBP1DIST DB2P_CTL 246
DB2PSPU1 DB2P_CTL 242
DB2PSPS2 DB2P_CTL 255
DBH1DBM1 DB2P_CTL 246
DBK1DIST DB2P_CTL 246
DBK1DBM1 DB2P_CTL 246
DBH1DIST DB2P_CTL 246
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Gerhard Adam
> Sent: 05 April, 2018 13:23
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WLM and Dispatching Priority
>
> Has anyone ever seen something like this before? Two started tasks
> {both
> DB2 address spaces] in the same service class and yet have different
> dispatching priorities? This screen capture shows the essential
> details.
>
> Any thoughts?
>
>
>
>
>
> Adam
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
For information, services and offers, please visit our web site:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=BsPGKdq7-Vl8MW2-WOWZjlZ0NwmcFSpQCLphNznBSDQ=N6F9BCgUHwZusdX8ZyCyU2jwc4Pymcw9q5eAiUx-I40=mPX-a6u383YitKnpjBFg_MUX_WJOsr8-U2CxRT-AQJs=
. This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee,
you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful. If
you have received this e-mail by error, please notify the sender
immediately by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission
of this e-mail or any attachments, nor responsible for any delay in
receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered
number 33014286
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Possible bug in reporting tool? (SDSF, RMF, 3rd Party).
Never heard of this, however, if WLM CICS Transaction Management is involved, I
can see where it might happen.
Also, DB2 is smart enough to alter DP's if it thinks it needs to.
I would ask IBM for an explanation.
Hopefully you are recording SMF99's and relevant DB2 information.
HTH,
Has anyone ever seen something like this before? Two started tasks {both
DB2 address spaces] in the same service class and yet have different
dispatching priorities? This screen capture shows the essential details.
Any thoughts?
::DISCLAIMER::
--
The contents of this e-mail and any attachment(s) are confidential and intended
for the named recipient(s) only. E-mail transmission is not guaranteed to be
secure or error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or may contain viruses in transmission.
The e mail and its contents (with or without referred errors) shall therefore
not attach any liability on the originator or HCL or its affiliates. Views or
opinions, if any, presented in this email are solely those of the author and
may not necessarily reflect the views or opinions of HCL or its affiliates. Any
form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written
consent of authorized representative of HCL is strictly prohibited. If you have
received this email in error please delete it and notify the sender
immediately. Before opening any email and/or attachments, please check them for
viruses and other defects.
--
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Why shouldn't they? WLM manages Goals and uses all resources, including DPTRY,
to realize them.
I see this now:
Jobname SrvClass CUR
PTY
MZCMT01A BAT_PJ220
COECM01L BAT_PJ224
MZFFB03B BAT_PJ214
DBP1DBM1 DB2P_CTL 246
DBP1DIST DB2P_CTL 246
DB2PSPU1 DB2P_CTL 242
DB2PSPS2 DB2P_CTL 255
DBH1DBM1 DB2P_CTL 246
DBK1DIST DB2P_CTL 246
DBK1DBM1 DB2P_CTL 246
DBH1DIST DB2P_CTL 246
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Gerhard Adam
> Sent: 05 April, 2018 13:23
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: WLM and Dispatching Priority
>
> Has anyone ever seen something like this before? Two started tasks
> {both
> DB2 address spaces] in the same service class and yet have different
> dispatching priorities? This screen capture shows the essential
> details.
>
> Any thoughts?
>
>
>
>
>
> Adam
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Gerhard Adam wrote:
>Has anyone ever seen something like this before? Two started tasks {both DB2
>address spaces] in the same service class and yet have different dispatching
>priorities? This screen capture shows the essential details.
What screen print? I only see white letters on a white background... ;-D
Perhaps you should re-post your question with more details using some
copy/paste actions?
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Has anyone ever seen something like this before? Two started tasks {both
DB2 address spaces] in the same service class and yet have different
dispatching priorities? This screen capture shows the essential details.
Any thoughts?
Adam
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
It is recommended to run the SYSVIEW started tasks in the WLM service class SYSSTC. Since SYSVIEW is a monitoring product, it is important for the STCs to have the high priority associated with this class in times of problem determination. With regard to the SYSVIEW CICSLOGR subtasks and CICS address spaces, the SYSVIEW address space (Main or Aux) that execute 1 or more CICSLOGR tasks need to run at a higher or at least equal dispatching priority with relation to CICS address spaces. Why is this needed? SYSVIEW for CICS data collection monitors and collects information about each and every CICS transaction that executes. At transaction termination, SYSVIEW will log the collected transaction information in the form of an SMF record to SMF and/or SYSVIEW log streams via the MVS logger. The collected transaction information is sent from the CICS address space to the SYSVIEW Main data collection or Auxiliary address space for logging via a PC. The data will be buffered in the SYSVIEW address space for a short period prior to logging. The information is shipped out of the CICS region so that additional processing and potential I/O conflicts do not potentially impact the throughput and execution of CICS transactions. As previously said, the data will be buffered in the SYSVIEW address space prior to logging. If the SYSVIEW address space which executes the subtasks known as CICSLOGRs is unable to execute or is not dispatched due to WLM policy, then the monitoring data will continue to be buffered. There is a limit to the amount of data that can or will be buffered. If the buffers become full, data will eventually need to be discarded. Multiple CICSLOGR subtasks can be defined to logically group CICS applications. The CICSLOGRs can execute in the SYSVIEW Main or Auxiliary address space. The configuration of CICSLOGRs subtasks should be planned in terms of application data groups as well as potential storage usage. Too many subtasks in an address space can exhaust the storage. The SYSVIEW Auxiliary address spaces can be used to execute CICSLOGR subtasks. Using the SYSVIEW Auxiliary address spaces can be a good way to separate workload and control storage usage. Todd J. Gagle CA Technologies Principal Software Architect Team SYSVIEW - Mainframe Enterprise Systems -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
On Thu, 26 Nov 2015 21:08:28 +, Martin Packer wrote: >I'm puzzled: Why do you think those dispatching priorities are >inconsistent with the WLM goals DP are (almost ?) *never* inconsistent with sane WLM goals. PI is usually a better indicator of out-of-whack goals. > (and your technical business goals)? Tran based goals, once active, make the region goal irrelevant. As already mentioned, running high priority tasks in a velocity class is pointless. John Arwe expounded on the vagaries of velocity years ago. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
I'm puzzled: Why do you think those dispatching priorities are inconsistent with the WLM goals (and your technical business goals)? Cheers, Martin Martin Packer, zChampion, Principal Systems Investigator, Worldwide Cloud & Systems Performance, IBM +44-7802-245-584 email: martin_pac...@uk.ibm.com Twitter / Facebook IDs: MartinPacker Blog: https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker From: phil yogendran <philyo...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 26/11/2015 19:20 Subject: WLM and Dispatching Priority Sent by:IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Hello All, I need some assistance with being able to get a proper DP assigned to a set of tasks. The problem is this; I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a subtask attached by SYSVIEW. In WLM, SYSVIEW is set to a service class of 'monitor' with an importance of 1 and velocity of 75. The CICS regions are set to a service class of 'CICSA' which has an importance of 1 and velocity goal of 65. However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW is at F4. How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on z/OS 1.13 and in a sysplex environment. Looking forward to your response. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
WLM and Dispatching Priority
Hello All, I need some assistance with being able to get a proper DP assigned to a set of tasks. The problem is this; I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a subtask attached by SYSVIEW. In WLM, SYSVIEW is set to a service class of 'monitor' with an importance of 1 and velocity of 75. The CICS regions are set to a service class of 'CICSA' which has an importance of 1 and velocity goal of 65. However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW is at F4. How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on z/OS 1.13 and in a sysplex environment. Looking forward to your response. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
First: DP's are variable and adjusted by WLM such that the task meets its goals. Apparently WLM in convinced that it is doing its job well. Second: you can move the critical monitors to Service Class SYSSTC. I don't think the CPUCRITICAL attribute will help in your current setup, because both SC's have the same importance. Kees. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of phil yogendran Sent: 26 November, 2015 16:08 To: IBM-MAIN@LISTSERV.UA.EDU Subject: WLM and Dispatching Priority Hello All, I need some assistance with being able to get a proper DP assigned to a set of tasks. The problem is this; I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a subtask attached by SYSVIEW. In WLM, SYSVIEW is set to a service class of 'monitor' with an importance of 1 and velocity of 75. The CICS regions are set to a service class of 'CICSA' which has an importance of 1 and velocity goal of 65. However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW is at F4. How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on z/OS 1.13 and in a sysplex environment. Looking forward to your response. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
RES: WLM and Dispatching Priority
Hello, Generally it is recommended that "Monitors" should execute at SYSSTC. Atenciosamente / Regards / Saludos BANCO BRADESCO S.A. 4250 / DPCD Engenharia de Software Sistemas Operacionais Mainframes Ituriel do Nascimento Neto Tel: +55 11 3684-2177 R: 42177 3-1404 Fax: +55 11 3684-4427 Banco Bradesco. Patrocinador oficial dos Jogos Olímpicos e Paralímpicos Rio 2016. -Mensagem original- De: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Em nome de phil yogendran Enviada em: quinta-feira, 26 de novembro de 2015 13:08 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: WLM and Dispatching Priority Hello All, I need some assistance with being able to get a proper DP assigned to a set of tasks. The problem is this; I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a subtask attached by SYSVIEW. In WLM, SYSVIEW is set to a service class of 'monitor' with an importance of 1 and velocity of 75. The CICS regions are set to a service class of 'CICSA' which has an importance of 1 and velocity goal of 65. However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW is at F4. How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on z/OS 1.13 and in a sysplex environment. Looking forward to your response. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN AVISO LEGAL ...Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou legalmente privilegiada. Se você não for destinatário desta mensagem, desde já fica notificado de abster-se a divulgar, copiar, distribuir, examinar ou, de qualquer forma, utilizar a informação contida nesta mensagem, por ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu conteúdo em sua base de dados, registros ou sistema de controle. Fica desprovida de eficácia e validade a mensagem que contiver vínculos obrigacionais, expedida por quem não detenha poderes de representação. LEGAL ADVICE...This message is exclusively destined for the people to whom it is directed, and it can bear private and/or legally exceptional information. If you are not addressee of this message, since now you are advised to not release, copy, distribute, check or, otherwise, use the information contained in this message, because it is illegal. If you received this message by mistake, we ask you to return this email, making possible, as soon as possible, the elimination of its contents of your database, registrations or controls system. The message that bears any mandatory links, issued by someone who has no representation powers, shall be null or void. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Put monitors in SYSSTC. This gives them the second highest DP in the system. You cannot completely control the DP in Service Classes. - -teD - Original Message From: phil yogendran Sent: Thursday, November 26, 2015 11:02 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: WLM and Dispatching Priority Hello All, I need some assistance with being able to get a proper DP assigned to a set of tasks. The problem is this; I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a subtask attached by SYSVIEW. In WLM, SYSVIEW is set to a service class of 'monitor' with an importance of 1 and velocity of 75. The CICS regions are set to a service class of 'CICSA' which has an importance of 1 and velocity goal of 65. However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW is at F4. How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on z/OS 1.13 and in a sysplex environment. Looking forward to your response. Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
Thank you all for your response and advise. My only reservation is that SYSVIEW, at times, tends to be heavy-footed and causes the system to 'pause'. This is only because of the data we capture at periodic intervals. Anyway, that's for me to investigate further and fix. Thanks, again, On Thu, Nov 26, 2015 at 11:16 AM, Ted MacNEIL <eamacn...@yahoo.ca> wrote: > Put monitors in SYSSTC. > This gives them the second highest DP in the system. You cannot completely > control the DP in Service Classes. > > - > -teD > - > Original Message > From: phil yogendran > Sent: Thursday, November 26, 2015 11:02 > To: IBM-MAIN@LISTSERV.UA.EDU > Reply To: IBM Mainframe Discussion List > Subject: WLM and Dispatching Priority > > Hello All, > > I need some assistance with being able to get a proper DP assigned to a set > of tasks. The problem is this; > > I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a > subtask attached by SYSVIEW. > > In WLM, SYSVIEW is set to a service class of 'monitor' with an importance > of 1 and velocity of 75. > > The CICS regions are set to a service class of 'CICSA' which has an > importance of 1 and velocity goal of 65. > > However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW > is at F4. > > How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on > z/OS 1.13 and in a sysplex environment. > > Looking forward to your response. Thanks. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
RES: WLM and Dispatching Priority
You were talking about your monitors, that were using an importance 1 SC instead of SYSSTC. And what about RMF ? RMF must be SYSSTC too. Atenciosamente / Regards / Saludos BANCO BRADESCO S.A. 4250 / DPCD Engenharia de Software Sistemas Operacionais Mainframes Ituriel do Nascimento Neto Tel: +55 11 3684-2177 R: 42177 3-1404 Fax: +55 11 3684-4427 Banco Bradesco. Patrocinador oficial dos Jogos Olímpicos e Paralímpicos Rio 2016. -Mensagem original- De: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Em nome de phil yogendran Enviada em: quinta-feira, 26 de novembro de 2015 14:53 Para: IBM-MAIN@LISTSERV.UA.EDU Assunto: Re: WLM and Dispatching Priority Thank you all for your response and advise. My only reservation is that SYSVIEW, at times, tends to be heavy-footed and causes the system to 'pause'. This is only because of the data we capture at periodic intervals. Anyway, that's for me to investigate further and fix. Thanks, again, On Thu, Nov 26, 2015 at 11:16 AM, Ted MacNEIL <eamacn...@yahoo.ca> wrote: > Put monitors in SYSSTC. > This gives them the second highest DP in the system. You cannot completely > control the DP in Service Classes. > > - > -teD > - > Original Message > From: phil yogendran > Sent: Thursday, November 26, 2015 11:02 > To: IBM-MAIN@LISTSERV.UA.EDU > Reply To: IBM Mainframe Discussion List > Subject: WLM and Dispatching Priority > > Hello All, > > I need some assistance with being able to get a proper DP assigned to a set > of tasks. The problem is this; > > I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a > subtask attached by SYSVIEW. > > In WLM, SYSVIEW is set to a service class of 'monitor' with an importance > of 1 and velocity of 75. > > The CICS regions are set to a service class of 'CICSA' which has an > importance of 1 and velocity goal of 65. > > However, what I see is that the CICS regions run at a DP of F6 and SYSVIEW > is at F4. > > How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on > z/OS 1.13 and in a sysplex environment. > > Looking forward to your response. Thanks. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN AVISO LEGAL ...Esta mensagem é destinada exclusivamente para a(s) pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou legalmente privilegiada. Se você não for destinatário desta mensagem, desde já fica notificado de abster-se a divulgar, copiar, distribuir, examinar ou, de qualquer forma, utilizar a informação contida nesta mensagem, por ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu conteúdo em sua base de dados, registros ou sistema de controle. Fica desprovida de eficácia e validade a mensagem que contiver vínculos obrigacionais, expedida por quem não detenha poderes de representação. LEGAL ADVICE...This message is exclusively destined for the people to whom it is directed, and it can bear private and/or legally exceptional information. If you are not addressee of this message, since now you are advised to not release, copy, distribute, check or, otherwise, use the information contained in this message, because it is illegal. If you received this message by mistake, we ask you to return this email, making possible, as soon as possible, the elimination of its contents of your database, registrations or controls system. The message that bears any mandatory links, issued by someone who has no representation powers, shall be null or void. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: WLM and Dispatching Priority
True, RMF is SYSSTC. Clearly there's more faith and confidence here. On Thu, Nov 26, 2015 at 1:39 PM, ITURIEL DO NASCIMENTO NETO < 4254.itur...@bradesco.com.br> wrote: > You were talking about your monitors, that were using an importance 1 SC > instead of SYSSTC. And what about RMF ? RMF must be SYSSTC too. > > Atenciosamente / Regards / Saludos > > BANCO BRADESCO S.A. > 4250 / DPCD Engenharia de Software > Sistemas Operacionais Mainframes > Ituriel do Nascimento Neto > Tel: +55 11 3684-2177 R: 42177 3-1404 > Fax: +55 11 3684-4427 > > > > > Banco Bradesco. > Patrocinador oficial dos Jogos Olímpicos e Paralímpicos Rio 2016. > > -Mensagem original- > De: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Em > nome de phil yogendran > Enviada em: quinta-feira, 26 de novembro de 2015 14:53 > Para: IBM-MAIN@LISTSERV.UA.EDU > Assunto: Re: WLM and Dispatching Priority > > Thank you all for your response and advise. My only reservation is that > SYSVIEW, at times, tends to be heavy-footed and causes the system to > 'pause'. This is only because of the data we capture at periodic intervals. > Anyway, that's for me to investigate further and fix. > > Thanks, again, > > > On Thu, Nov 26, 2015 at 11:16 AM, Ted MacNEIL <eamacn...@yahoo.ca> wrote: > > > Put monitors in SYSSTC. > > This gives them the second highest DP in the system. You cannot > completely > > control the DP in Service Classes. > > > > - > > -teD > > - > > Original Message > > From: phil yogendran > > Sent: Thursday, November 26, 2015 11:02 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Reply To: IBM Mainframe Discussion List > > Subject: WLM and Dispatching Priority > > > > Hello All, > > > > I need some assistance with being able to get a proper DP assigned to a > set > > of tasks. The problem is this; > > > > I have 2 tasks, SYSVIEW and CICSLOGR and many CICS tasks. CICSLOGR is a > > subtask attached by SYSVIEW. > > > > In WLM, SYSVIEW is set to a service class of 'monitor' with an importance > > of 1 and velocity of 75. > > > > The CICS regions are set to a service class of 'CICSA' which has an > > importance of 1 and velocity goal of 65. > > > > However, what I see is that the CICS regions run at a DP of F6 and > SYSVIEW > > is at F4. > > > > How can I make sure that SYSVIEW and CICSLOGR run at a higher DP? I'm on > > z/OS 1.13 and in a sysplex environment. > > > > Looking forward to your response. Thanks. > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > AVISO LEGAL ...Esta mensagem é destinada exclusivamente para a(s) > pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou > legalmente privilegiada. Se você não for destinatário desta mensagem, desde > já fica notificado de abster-se a divulgar, copiar, distribuir, examinar > ou, de qualquer forma, utilizar a informação contida nesta mensagem, por > ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que > nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu > conteúdo em sua base de dados, registros ou sistema de controle. Fica > desprovida de eficácia e validade a mensagem que contiver vínculos > obrigacionais, expedida por quem não detenha poderes de representação. > LEGAL ADVICE...This message is exclusively destined for the people to > whom it is directed, and it can bear private and/or legally exceptional > information. If you are not addressee of this message, since now you are > advised to not release, copy, distribute, check or, otherwise, use the > information contained in this message, because it is illegal. If you > received this message by mistake, we ask you to return this email, making > possible, as soon as possible, the elimination of its contents of your > database, registrations or controls system. The message that bears any > mandatory links, issued by someone who has no representation powers, shall > be null or void. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
