Defined capacity

[R.S.]

I'm trying to understand how to set up Defined Capacity for an LPAR.
Unfortunately HMC help is not helpful and software manuals do not
provide details about the settings.

My goal is to set up Defined Capacity for one LPAR. No groups.

A record from Change LPAR Controls:
LPAR: LP1
Active: Yes
Def. Capacity: 45 --> it's MSU isn't it?
WLM: (checkbox) --> what is it for???
Curr. Weight: 15
Initial Weight: 15
Min. Weight: (empty) --> a field appears only when WLM is checked
Max. Weight: (empty) --> as above - only when WLM checkbox is checked
Current Capping: No
Initial Capping: (checkbox) unchecked
Num. of dedicated processors: 0
Number of Not dedicated Proc.: 2


My questions:
1. Defined Capacity in the above record is expressed in MSU. T/F?

2. What is the purpose of WLM checkbox?

3. Initial capping must be unchecked to make softcapping effective. What
about initial capping for zIIP or zAAP?
I observed that capping of zIIP precludes WLM checkbox ("greyed" field)

4. Remarks, comments, hints?

--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive.

BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: in...@brebank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP: 526-021-50-88.
Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN

[Vernooij, CP - SPLXM]

You can check manuals:
- z/OS V1R11.0 MVS Planning Workload Management z/OS V1R10.0-V1R11.0 ch: Workload Management and Workload License Charges
- z/OS V1R11.0 Planning for Subcapacity Pricing z/OS V1R10.0-V1R11.0 ch: More about defined capacity (and surrounding chapters).


Answers:
1. Yes.
2. To use together with IRD.
3. No idea.
4.>
I suppose you want to control the 4 hour running average of the LPAR, because that is what it does.
Read the information about weights and how WLM imposes the 4HrRA to the LPAR, either with phantom load or with a (to be avoided) capping pattern.

Kees.

********************************************************
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
********************************************************

[Vernooij, CP - SPLXM]

Check this paper too:
http://www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH&appname=STGE_ZS_ZS_USEN&htmlfid=ZSW03077USEN&attachment=ZSW03077USEN.PDF

kees.

-----Original Message-----
From: Vernooij, CP - SPLXM
Sent: Tuesday, February 12, 2013 13:46
To: IBM Mainframe Discussion List
Subject: RE: Defined capacity

You can check manuals:
- z/OS V1R11.0 MVS Planning Workload Management z/OS V1R10.0-V1R11.0 ch: Workload Management and Workload License Charges
- z/OS V1R11.0 Planning for Subcapacity Pricing z/OS V1R10.0-V1R11.0 ch: More about defined capacity (and surrounding chapters).


Answers:
1. Yes.
2. To use together with IRD.
3. No idea.
4.>
I suppose you want to control the 4 hour running average of the LPAR, because that is what it does.
Read the information about weights and how WLM imposes the 4HrRA to the LPAR, either with phantom load or with a (to be avoided) capping pattern.

Kees.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of R.S.
Sent: Tuesday, February 12, 2013 13:26
To: IBM-...@LISTSERV.UA.EDU
Subject: Defined capacity

Tre�� tej wiadomo�ci mo�e zawiera� informacje prawnie chronione Banku przeznaczone wy��cznie do u�ytku s�u�bowego adresata. Odbiorc� mo�e by� jedynie jej adresat z wy��czeniem dost�pu os�b trzecich. Je�eli nie jeste� adresatem niniejszej wiadomo�ci lub pracownikiem upowa�nionym do jej przekazania adresatowi, informujemy, �e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dzia�anie o podobnym charakterze jest prawnie zabronione i mo�e by� karalne. Je�eli otrzyma�e� t� wiadomo�� omy�kowo, prosimy niezw�ocznie zawiadomi� nadawc� wysy�aj�c odpowied� oraz trwale usun�� t� wiadomo�� w��czaj�c w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive.

BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: in...@brebank.pl S�d Rejonowy dla m. st. Warszawy XII Wydzia� Gospodarczy Krajowego Rejestru S�dowego, nr rejestru przedsi�biorc�w KRS 0000025237, NIP: 526-021-50-88.
Wed�ug stanu na dzie� 01.01.2013 r. kapita� zak�adowy BRE Banku SA (w ca�o�ci wp�acony) wynosi 168.555.904 z�otych.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to list...@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
********************************************************

[R.S.]

W dniu 2013-02-12 13:50, Vernooij, CP - SPLXM pisze:

> Check this paper too:
> http://www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH&appname=STGE_ZS_ZS_USEN&htmlfid=ZSW03077USEN&attachment=ZSW03077USEN.PDF
>
> kees.

Kees,
Thank you for quick response. Actually I have 3 open documents on my PC,
exactly the same which you mentioned ;-)
I found and answer for Q1 (MSU as a unit), which I was 99% sure.

Unfortunately I found no explanation about WLM checkbox. From your
response I assume I should leave it unchecked, since I don't use IRD.

Regarding Q3 - I found that Initial Capping on any processor-type tab
gives the same result - it disables WLM checkbox. So I assume, I
shouldn't use Initial Capping for any CP type, including zIIP.


BTW: General observation. It is typical for IBM - Software manuals avoid
describing any details about hardware panels, while H/W manuals do not
describe the meaning of the fields and panels.

[Vernooij, CP - SPLXM]

Radoswaw,

One to the manuals has a chapter IRD, I think you will find there that the WLM checkbox triggers IRDs weight management.
From my experience: forget IRD on modern machines. CPU management is disabled by Hiperdispatch and weight management and softcapping do not cooperate.

Kees.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of R.S.

********************************************************
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
********************************************************

[R.S.]

"To enable the WorkLoad Manager (WLM), select Enable workload manager.
Selecting WLM from one processor details automatically selects WLM from
the other processor details and conversely. Specify the minimum and
maximum processing weights. Change LPAR management weights based on
customer policies and current work loads. "

Indeed, to enable WLM I have to check "Enable WLM". I wouldn't know that!
Of course there is no explanation what does it mean "enable WLM". WLM is
enabled on every z/OS image and cannot be disabled. So, there must be
some other explanation of the words above. IRD? No clue about IRD.


However I found "WLM checkbox" in the chapter about IRD:
"For each logical partition that will participate in LPAR weight
management, do the following:

- Make sure that "Initial Capping" is turned off. WLM cannot
manage the weight of a logical partition that is capped.

- Enter the initial processing weight. This becomes the logical
partition's weight when it is first IPLed.

- Enter the minimum and maximum weights. These set the lower and
upper limits for the weights that WLM will assign to the logical partition.

- Check the "WLM Managed" box. This is the final step in
activating LPAR weight management." ---> THAT'S THE CHECKBOX!



BTW: I never used IRD for simple reason: lack of sysplex.


So, to my knowledge:
WLM checkbox - used only for IRD, leave unchecked otherwise.
Defined Capacity - simply put non-zero value, uncheck Initial Capping on
CP, zIIP, zAAP.


Thank you Kees!

--
Radoslaw Skorupka
Lodz, Poland

P.S.
I just found another "helpful" explanation:
Image Pforile, Options tab:

"CP management cluster name

The name specified for the CP management cluster. "

I suspect it's also IRD related stuff.








W dniu 2013-02-12 14:58, Vernooij, CP - SPLXM pisze:

> .

[Vernooij, CP - SPLXM]

Yes, LPAR Clusters are IRD managed groups of LPARs.

Don't forget to read about Weight in relation to 'phantom load' and 'capping pattern', to avoid erratic Lpar performance.

I always like to have a monitor telling what is going on in the system, so I will not be surprised by angry telephone calls and have no clue where to start looking. I use Mainview, I don't know RMF, but it probably also displays the 4HrRA, the current LPAR utilization and the status of softcapping, so you know why the system is doing what it is doing.

HTH,

[Jan Vanbrabant]

Hi Kees,

I'm following this thread. (Learning a lot doing this...)

Whare can I find more about 'phantom load' and 'capping pattern'?
Didn't find these terms in de 2 WLM manuals you mentioned earlier:

SA22-7602-19 z/OS V1R12.0 MVS Planning Workload Management
SA22-7999-06 z/OS V1R12.0 Planning for Subcapacity Pricing

(I am at R12, so I looked in the R12 manuals)

Jan

[Fabio Massimo Ottaviani]

Hi Jan
Redbook - WLM System Programmer Guide - Chapter 3
Best regards
Fabio
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Fabio Massimo Ottaviani
+ EPV Technologies Technical Director
+ Skype: fabio.massimo.ottaviani
+ Mobile: +393406168088
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ IT Cost under Control
+ www.epvtech.com
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 Please consider the environment - do you really need to print this email?

-----Messaggio originale-----
Da: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] Per conto di Jan Vanbrabant
Inviato: mercoledì 13 febbraio 2013 17:13
A: IBM-...@LISTSERV.UA.EDU
Oggetto: Re: Defined capacity

> > Treść tej wiadomości może zawierać informacje prawnie chronione
> > Banku

> przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może
> być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli
> nie jesteś adresatem niniejszej wiadomości lub pracownikiem
> upoważnionym do jej przekazania adresatowi, informujemy, że jej
> rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o
> podobnym charakterze jest prawnie zabronione i może być karalne.
> Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie
> zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość

> włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

> >
> > This e-mail may contain legally privileged information of the Bank
> > and
> is intended solely for business use of the addressee. This e-mail may
> only be received by the addressee and may not be disclosed to any third parties.
> If you are not the intended addressee of this e-mail or the employee
> authorised to forward it to the addressee, be advised that any
> dissemination, copying, distribution or any other similar activity is
> legally prohibited and may be punishable. If you received this e-mail
> by mistake please advise the sender immediately by using the reply
> facility in your e-mail software and delete permanently this e-mail
> including any copies of it either printed or saved to hard drive.
> >
> > BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829
> > 00 00,
> fax +48 (22) 829 00 33, www.brebank.pl, e-mail: in...@brebank.pl

> > Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego
> Rejestru Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP:
> 526-021-50-88.
> > Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA
> > (w
> całości wpłacony) wynosi 168.555.904 złotych.
> >
> >
> > --------------------------------------------------------------------

> Treść tej wiadomości może zawierać informacje prawnie chronione Banku
> przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może
> być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli
> nie jesteś adresatem niniejszej wiadomości lub pracownikiem
> upoważnionym do jej przekazania adresatowi, informujemy, że jej
> rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o
> podobnym charakterze jest prawnie zabronione i może być karalne.
> Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie
> zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość

> włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

>
> This e-mail may contain legally privileged information of the Bank and
> is intended solely for business use of the addressee. This e-mail may
> only be received by the addressee and may not be disclosed to any
> third parties. If you are not the intended addressee of this e-mail or
> the employee authorised to forward it to the addressee, be advised
> that any dissemination, copying, distribution or any other similar
> activity is legally prohibited and may be punishable. If you received
> this e-mail by mistake please advise the sender immediately by using
> the reply facility in your e-mail software and delete permanently this
> e-mail including any copies of it either printed or saved to hard drive.
>
> BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00
> 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: in...@brebank.pl

> Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego
> Rejestru Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP:
> 526-021-50-88.
> Według stanu na dzień 01.01.2013 r. kapitał zakładowy BRE Banku SA (w
> całości wpłacony) wynosi 168.555.904 złotych.
>
>

[Dave Barry]

Kees,

I'd like to know more about the lack of cooperation between weight management and softcapping. Can you enlighten us?

Much obliged,
db

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Vernooij, CP - SPLXM
Sent: Tuesday, February 12, 2013 8:59 AM
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

Radoswaw,

One to the manuals has a chapter IRD, I think you will find there that the WLM checkbox triggers IRDs weight management.
From my experience: forget IRD on modern machines. CPU management is disabled by Hiperdispatch and weight management and softcapping do not cooperate.

Kees.

[Jan Vanbrabant]

I second Dave's question, Kees.
jan

[Martin Packer]

Maybe he's just pointing out that IRD Weight Management and Softcapping
are two separate concepts/knobs/dials.

Cheers, Martin

Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking Center of Excellence, IBM

+44-7802-245-584

email: martin...@uk.ibm.com

Twitter / Facebook IDs: MartinPacker
Blog:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker

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

[Al Sherkow]

The "initial capping" checkbox on the HMC is the original (back to the 3090?) PR/SM Hard Capping control. HardCapped LPARs do not work with Defined Capacity or LPAR Group Capacity Limits.

Al Sherkow, I/S Management Strategies, Ltd.
Consulting Expertise on IBM Workload License Charges (WLC),
LPARs and LCS Software
Seminars on IBM Mainframe Software Pricing
+1 414 332-3062

[Al Sherkow]

IRD weight management and Defined Capacity work fine.

The problem comes with IRD and LPAR Group Capacity Limits (introduced in z/OS 1.8). The problem is when an LPAR Group is capped IRD stops adjusting weights. This is rather unfortunate as this is the time when a customer would most want IRD to adjust the weights within the limits of the LPAR Group Limit.

When a group of LPARs is capped the effect is the same as that group being out of capacity. That is there is more workload trying to run than the amount of capacity available. When this group cap is set some LPARs may be running low importance work consuming CPU time in the group. Simultaneously other LPARs may really be feeling the capacity stress and these may stop running importance 4, 5 and discretionary work. At this point is would be great if IRD would move capacity away from the low importance work in the group, to the LPARs that are impacting more important work. This is what IRD weight management would do.

You can use both of these capabilities together, but you must understand that weight management stops, as it is at the time the group cap "turns on".

[Vernooij, CP - SPLXM]

Hi Al,

Back from holidays, I was reading the requests about IRD and DC/GCL and saw you answered them.

My understanding is however, that IRD Weight management stops, "when an LPAR is softcapped", both by the Defined Capacity and by the Group Capacity Limit.

This is probably explainable, because GCL takes the current Weights into consideration when distributing the GC MSUs over the LPARs and cannot handle weights being manipulated behind its back by IRD. However IRD in fact is also WLM, so these components could have coordinated their actions, but don't.

As you describe, this is very undesirable and can cause problems.

I opened an PRM at IBM to check this behavior and they confirmed this.
I also asked what happens when I stop IRD. Then the weights are kept at their current, probably unusable values.
Also IBM answered that they had no intention to change this, so this makes me conclude that IRD and DC/GCL do not cooperate, in fact they do the opposite, resulting in undesired LPAR settings.

Kees.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Al Sherkow
Sent: Friday, February 15, 2013 17:03
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

********************************************************
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
********************************************************

[Al Sherkow]

I have discussed the problem of IRD and GCL with multiple clients and with IBM. That this exists is certain. Also I heart that IBM does not intend to fix this. Unfortunate decision in my opinion; and not good for the mainframe ecosystem.

I have never discussed a problem with IRD and Defined Capacity by itself. I'm interested to continue the discussion of IRD and DC if someone wants to share their experience.

Regards, Al

Al Sherkow, I/S Management Strategies, Ltd.
Consulting Expertise on IBM Workload License Charges (WLC)

[Vernooij, CP - SPLXM]

Al,

To clarify my statement, if needed: when I set up the z196's with GCL, I did a lot of research on what tools were available and which were usable. There I read, that IRD Weight management is stopped when an LPAR is "soft capped". I do not remember whether I interpreted this as being capped by both DC and GCL, or that I actually read this. I have never used it, so I don't have experience with the combination of the tools.

Kees.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Al Sherkow
Sent: Monday, February 25, 2013 19:11
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

********************************************************
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
********************************************************

[Al Sherkow]

Ok, that is better. The term "softcapped" could apply to either LPAR Defined Capacity or LPAR Group Capacity Limits.


Let's try to clear this up. LPAR Defined Capacity works with or without IRD as expected. LPAR Defined Capacity also works well when used with LPAR Group Capacity Limits.

What does not work as you might expect is LPAR Group Capacity Limits and IRD Weight Management, as IRD stops adjusting weights when the LPAR Group Capacity Limit is limiting the group (or softcapping the group) .

Al Sherkow, I/S Management Strategies, Ltd.

Consulting Expertise on IBM Workload License Charges (WLC),
LPARs and LCS Software

[Vernooij, CP - SPLXM]

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Al Sherkow
Sent: Tuesday, February 26, 2013 19:18
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

> Ok, that is better. The term "softcapped" could apply to either LPAR Defined Capacity or LPAR Group Capacity Limits.


> Let's try to clear this up. LPAR Defined Capacity works with or without IRD as expected. LPAR Defined Capacity also works well when used with LPAR Group Capacity Limits.

Agreed. We use the combination of GCL and DC.

> What does not work as you might expect is LPAR Group Capacity Limits and IRD Weight Management, as IRD stops adjusting weights when the LPAR Group Capacity Limit is limiting the group (or softcapping the group) .

Agreed.
I was under the impression, but not sure, that IRD also stops adjusting weights when DC is softcapping an LPAR. I have been trying to find where I read that, but as usual IBM has messed up (reorganized) its website again, so all my links return only 404's. On the other hand, I recently talked to another site, who are using zCOST (which manipulates DCs) and IRD together and AFAIK they did not have problems with the combination.

Al Sherkow, I/S Management Strategies, Ltd.
Consulting Expertise on IBM Workload License Charges (WLC), LPARs and LCS Software

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to list...@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
********************************************************

[Mary Anne Matyaz]

I haven't been following this thread too closely, but I thought perhaps a recent presentation could help. Kathy Walsh did "Configuring LPARs for Performance" at SHARE. She discusses several of the topics you are discussing.

https://share.confex.com/share/120/webprogram/Handout/Session13101/lpar_perf.pdf

MA

[Vernooij, CP - SPLXM]

Mary Ann,

Great tip. All scattered info, which took me days to find, now bundled into one presentation.

Thanks,
Kees.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Mary Anne Matyaz
Sent: Tuesday, February 26, 2013 20:32
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

********************************************************
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
********************************************************

[Vernooij, CP - SPLXM]

Hi Al and Horst,

I found the source of my impression that IRD weight management is also being stopped by 'softcapping'.

The document is " z/OS Workload Management Update for z/OS V1.11 and V1.12" by Horst Sinram
IBM Germany Research & Development August 2, 2010.

Sheet 17 (Group Capacity: Summary) states:

Working with IRD CPU Weight Management
• Defined and Group Capacity work with IRD but Weight Changes are only possible for partitions
which are not being capped (or subject to capping)

This at least suggests that IRD Weight Management is also disabled when an Lpar is softcapped by DC limits and not only by GC limits.

Horst,
Can you clarify this?

Kees.

-----Original Message-----
From: Vernooij, CP - SPLXM
Sent: Tuesday, February 26, 2013 19:33
To: IBM Mainframe Discussion List
Subject: RE: Defined capacity

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Al Sherkow
Sent: Tuesday, February 26, 2013 19:18
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

> Ok, that is better. The term "softcapped" could apply to either LPAR Defined Capacity or LPAR Group Capacity Limits.


> Let's try to clear this up. LPAR Defined Capacity works with or without IRD as expected. LPAR Defined Capacity also works well when used with LPAR Group Capacity Limits.

Agreed. We use the combination of GCL and DC.

> What does not work as you might expect is LPAR Group Capacity Limits and IRD Weight Management, as IRD stops adjusting weights when the LPAR Group Capacity Limit is limiting the group (or softcapping the group) .

Agreed.
I was under the impression, but not sure, that IRD also stops adjusting weights when DC is softcapping an LPAR. I have been trying to find where I read that, but as usual IBM has messed up (reorganized) its website again, so all my links return only 404's. On the other hand, I recently talked to another site, who are using zCOST (which manipulates DCs) and IRD together and AFAIK they did not have problems with the combination.

Al Sherkow, I/S Management Strategies, Ltd.
Consulting Expertise on IBM Workload License Charges (WLC), LPARs and LCS Software

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to list...@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
********************************************************

[Horst Sinram]

> This at least suggests that IRD Weight Management is also disabled when an Lpar is softcapped by DC limits and not only by GC limits.

Kees:
Correct - when an LPAR is being capped, regardless whether that's due to an LPAR level defined capacity, or due to group capacity, IRD won't help the partition.

In the case of LPAR level DC that's likely no problem: The LPAR's 4-hour-rolling-average has exceeded the installation defined limit despite the fact that the LPAR already has a low weight. Granting it even more weight doesn't make much sense.
With group capping the situation is a bit different: the LPAR "weight" does also determine the LPAR's entitlement of the group capacity. With "weight" being the current (vs. initial) weight IRD may have contributed to managing the LPAR to a low entitlement. That can sometimes be problematic, e.g. depending on whether the importance distribution of your workload within the LPAR cluster has changed or not, and how long the capping situation persists (with pattern capping there is obviously a much better chance.)

Horst Sinram - IBM z/OS Workload Management

[Vernooij, CP - SPLXM]

Horst,

Thanks for the confirmation.

About pattern capping: I am not sure if this is much better. WLW will adapt the capping pattern to distribute to the LPAR the resources that it is entitled to, based on its (IRD modified) weights. So even then WLM will try to honour/sustain the IRD modified 'share' of that LPAR.
It is probably true, that during the uncapped parts of the pattern, IRD could have a chance to adjust weights, if this is what you mean by a 'better chance'.

We sometimes see that IBM Labs do not always cooperate as the customer might wish, but 2 WLM internal functions that do not cooperate, is at least surprising, if not annoying. Also the fact that stopping IRD leaves the weights at the values that just happen to be current at the moment of stopping, is no neat way to shut down. It's more like: if you don't need me anymore, then do sort out everything yourself. AFAIK, I must use the HMC to set the values again to their initial values (or do a POR ;-). Altogether, I did not dare to activate IRD after activating GCLs.

Kees.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Horst Sinram
Sent: Wednesday, February 27, 2013 19:03
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Defined capacity

********************************************************
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
********************************************************

[Horst Sinram]

> It is probably true, that during the uncapped parts of the pattern, IRD could have a chance to adjust weights, if this is what you mean by a 'better chance'.

Yes, exactly. (BTW, I don't want to promote pattern capping in general.)

>AFAIK, I must use the HMC to set the values again to their initial values (or do a POR ;-). Altogether, I did not dare to activate IRD after activating GCLs.

At the HMC, you could set MIN=MAX=INITIAL weight to enforce the weight setting that you want to implement and transition then.
Also, there are APIs that allow driving such changes automatically. These APIs could be used through some products (e.g. Tivoli System Automation ProcOps), or you could (probably, but I did not verify that all operations are supported e.g. in z/OS BCPii) come up with homegrown automation.