I got bit by a CP abend STL023 under VM 5.2 when I used LIMITHARD on one of my Linux guests using QDIO OSA. You should review VM63715. The fix i s included in VM 5.3.
Brian Nielsen On Thu, 2 Aug 2007 09:25:42 -0400, Anne Crabtree <[EMAIL PROTECTED]> wrote: >I think I'll try this and see how it goes... thanks ! > >Anne D. Crabtree >System Programmer >WV Dept of Administration - OT >304-558-1494 >Fax 304-558-1441 > >>>> [EMAIL PROTECTED] 8/2/2007 9:12 AM >>> >I use a combination of relative and absolute for some of my servers >such >as >this: > >SET SHARE LNXWEB RELATIVE 100 ABSOLUTE 50% LIMITHARD > >This should let LNXWEB use the processor at the same relative share as >th >e >other servers, but not let it use more than 50% of the processor. > >/Tom Kern >/301-903-2211 > > >On Thu, 2 Aug 2007 08:56:16 -0400, Anne Crabtree ><[EMAIL PROTECTED]> >wrote: > >>We have five linux instances running, two of which aren't really >being >>used, two are production and one is test. In the test linux >instance, >>they are running a web app (which I know nothing about). At certain >>times during the day, this test instance will take close to 100% of >the >>IFL. We want to back it off so that it can take no more than 50% to >see > >>how that affects them. Would it be logical to issue SET SHARE linux >>RELATIVE 50 since it is defaulting to REL 100? Will that do what I >>think and limit it to half of what the other virtual machines "get"? >> >>Anne D. Crabtree >>System Programmer >>WV Dept of Administration - OT >>304-558-1494 >>Fax 304-558-1441 >>======================== >======================== = >======================== >======================== ========================= ========================
