Table 6-8 shows the help for adding hardware resources. Table 6-8 Context-sensitive help for adding hardware resource provisioning Name and fast path Context-sensitive help (F1) Application Controller  Name This is the application controller for which you configure DLPAR and CoD  resource provisioning. Use desired level from  the LPAR profile There is no default value. You must make one of the following choices: GLYPH<SM590000> Enter  Yes  if you want the LPAR hosting your node to reach only the  level of resources that is indicated by the desired level of the LPAR’s  profile. By selecting  Yes , you trust the desired level of LPAR profile to  fit the needs of your application controller.  GLYPH<SM590000> Enter  No  if you prefer to enter exact optimal values for memory,  processor (CPU), or both. These optimal values match the needs of  your application controller, and you have better control of the level of  resources that are allocated to your application controller. GLYPH<SM590000> Enter nothing if you do not need to provision any resource for your  application controller.  For all application controllers that have this tunable set to  Yes , the  allocation that is performed lets the LPAR reach the LPAR desired value of  the profile.  Suppose that you have a mixed configuration, in which some application  controllers have this tunable set to  Yes , and other application controllers  have this tunable set to  No  with some optimal level of resources specified.  In this case, the allocation that is performed lets the LPAR reach the  desired value of the profile that is added to the optimal values. Optimal number of  gigabytes of memory  Enter the amount of memory that PowerHA SystemMirror attempts to  acquire for the node before starting this application controller.  This  Optimal number of gigabytes of memory  value can be set only if the  Used desired level from the LPAR profile  value is set to  No .  Enter the value in multiples of …, ‰, ¾, or 1 GB. For example, 1 represents  1 GB or 1024 MB, 1.25 represents 1.25 GB or 1280 MB, 1.50 represents  1.50 GB or 1536 MB, and 1.75 represents 1.75 GB or 1792 MB. If this amount of memory is not satisfied, PowerHA SystemMirror takes  resource group (RG) recovery actions to move the RG with this application  to another node. Alternatively, PowerHA SystemMirror can allocate less  memory depending on the  Start RG even if resources are  insufficient  cluster tunable. Optimal number of  dedicated processors Enter the number of processors that PowerHA SystemMirror attempts to  allocate to the node before starting this application controller.  This attribute is only for nodes running on an LPAR with Dedicated  Processing Mode. This  Optimal number of dedicated processors  value can be set only if  the  Used desired level from the LPAR profile  value is set to  No .  If this number of CPUs is not satisfied, PowerHA SystemMirror takes RG  recovery actions to move the RG with this application to another node.  Alternatively, PowerHA SystemMirror can allocate fewer CPUs depending  on the  Start RG even if resources are insufficient  cluster tunable. For more information about how to acquire mobile resources at the RG  onlining stage, see 6.6, “Introduction to resource acquisition” on page 198. For more information about how to release mobile resources at the RG  offlining stage, see 6.7, “Introduction  to the release of resources” on  page 207. 180  IBM PowerHA SystemMirror V7.2.3 for IBM AIX and V7.2.2 for Linux