Correct, and it even does not only hold true for a spike, but also for a heavy production job, that can run at full speed while driving up the 4HRA. How long it can run at full speed until the 4HRA reaches the limit and capping steps in, depends on the value of the 4HRA at the start of the job. This in turn depends on how much work has been run in the previous 4 hours, so whether you ran your private Bitcoin business there or not.
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: 16 January, 2015 14:43 To: [email protected] Subject: Re: z13 unanswered question. On Thu, Jan 15, 2015 at 11:25 PM, Timothy Sipples <[email protected]> wrote: > >Nor will I because it cost real money due > >to MSU usage and I'd get keel hauled for wasting money. > > First of all, I'm quite sure all computing has costs. Except.... > > ....Unutilized sub-peak 4HRA capacity is as close to free as anything in > computing. Your time is not free, though. > True and not true. We use "Group Capacity" to cap our MSUs.When you do this, you can exceed your hard cap if you have, what I call, some "saved up slack" from the previous 4HRA. And we actually monitor this with some code I have written to analyze SYSLOG messages written out from BMC' MainView. So, it is true that my Bit Coin mining would not really cost hard dollars. But it would impact this "reservoir" of MSUs which can be "tapped" for a short term "spike" of usage wherein we can exceed our "Group Capacity" for a short while before being "capped" by PR/SM. ******************************************************** 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 [email protected] with the message: INFO IBM-MAIN
