Parte da documentação da IBM sobre a opção "set share" que tem por finalidade definir a prioridade entre as vm's linux. #cp set share # #


De modo geral, a prioridade pode ser consultada através do comando:

* Todo os comandos abaixo, são executados na MAINT.

#cp q share linuxvm

Por default, todas as máquinas são criadas com o mesmo peso, sendo ele "100"

uma saída padrão do comando seria:

CP Q SHARE DTSD101
USER DTSD101 :  CP   RELATIVE SHARE = 100
                      MAXIMUM SHARE = NOLIMIT
                ZAAP RELATIVE SHARE = 100
                      MAXIMUM SHARE = NOLIMIT
                IFL  RELATIVE SHARE = 100
                      MAXIMUM SHARE = NOLIMIT
                ICF  RELATIVE SHARE = 100
                      MAXIMUM SHARE = NOLIMIT
                ZIIP RELATIVE SHARE = 100
                      MAXIMUM SHARE = NOLIMIT

Para definir a prioridade de forma bem simples e RELATIVA , use:

set share dtsd101 relative 50

USER DTSD101 :  CP   RELATIVE SHARE = 50

                      MAXIMUM SHARE = NOLIMIT

                ZAAP RELATIVE SHARE = 50

                      MAXIMUM SHARE = NOLIMIT

                IFL  RELATIVE SHARE = 50

                      MAXIMUM SHARE = NOLIMIT

                ICF  RELATIVE SHARE = 50

                      MAXIMUM SHARE = NOLIMIT

                ZIIP RELATIVE SHARE = 50

                      MAXIMUM SHARE = NOLIMIT

Ready; T=0.01/0.01 11:00:01

  Os termos RELATIVE e ABSOLUTE se referem ao fato de darem prioridade sobre as outras máquinas(RELATIVE), e o uso reservado e absoluto do processador real (ABSOLUTE)


Abaixo a baixa do manual do site IBM sobre o uso do comando.


SET SHARE Command

z/VM V5R4.0 Performance
SC24-6109-06

The SET SHARE command and the SHARE directory statement allow you to control the percentage of system resources a user receives. These system resources include processors, real storage, and paging I/O capability. With z/VM, a virtual machine receives its proportion of any scarce resource (a bottlenecked resource) according to its SHARE setting. Both the normal share and the maximum share can be set.

    * Normal share—The normal share is also known as the target minimum share. CP attempts to provide at least this amount of resources to a virtual machine if the virtual machine can use the resources.
    * Maximum share—CP attempts to limit a virtual machine from using more than this amount of system processor resources. The limit types that can be specified for the maximum share are:
          o NOLIMIT. A user is not limited. This is the default.
          o LIMITHARD. A user does not get more than the maximum share.
          o LIMITSOFT. A user does not get more than the maximum share, unless no other user can use the available resources.

The operands available with SET SHARE for both normal and maximum share are:

    * ABSOLUTE—An ABSOLUTE share allocates to a virtual machine an absolute percentage of all available system resources. For example, if you assign a virtual machine an absolute share of 50%, CP allocates to that virtual machine approximately 50% of all available resources (regardless of the number of other virtual machines running).
    * RELATIVE—A RELATIVE share allocates to a virtual machine a portion of the total system resources minus those resources allocated to virtual machines with an ABSOLUTE share. Also, a virtual machine with a RELATIVE share receives access to system resources that is proportional with respect to other virtual machines with RELATIVE shares. For example, if a virtual machine (VM1) has a RELATIVE share of 100, and a second virtual machine (VM2) has a RELATIVE share of 200, VM2 receives twice as much access to system resources as VM1.

      If a virtual machine serves multiple users, its relative share should be set to
      n × a normal single virtual machine share

      where n is the number of users normally expected to be contending concurrently for resources in that virtual machine.
    * INITIAL—An INITIAL share means that a virtual machine's access to system resources is reset to that specified in the virtual machine's directory entry.

Source:  http://publib.boulder.ibm.com/infocenter/zvm/v5r4/topic/com.ibm.zvm.v54.hcpb8/share.htm?resultof=%22%73%65%74%22%20%22%73%68%61%72%65%22%20