Getting the DLPAR resource information from the HMC Some people think only the available resources (the query method is shown in Table 6-16)  can be used for the DLPAR operation. Table 6-16 Get server’s available resources from HMC Memory lshwres -m <cec> --level sys -r mem -F curr_avail_sys_mem CPU lshwres -m <cec> --level sys -r proc -F curr_avail_sys_proc_units Tip:  The  lshwres  commands in Table 6-16 are examples, but it is not necessary for the  user to run these commands. These commands are embedded in to the ROHA run time,  and run as part of the ROHA acquisition and release steps. Strictly speaking, this situation is  not  correct. Two kinds of cases must be considered: GLYPH<SM590000> There are stopped partitions on the CEC. A stopped partition still keeps its resources because the resources do not appear as  Available  in the CEC. As a matter of fact, the resources are available for other LPARs.  Therefore, if you stopped a partition on the CEC, the resource that stopped the partition  must be available for the DLPAR operation. GLYPH<SM590000> There are uncapped mode partitions in the CEC. In an uncapped shared processor partition, considering only the maximum processor unit  is not correct. Consider the following case, where one LPAR’s profile includes the following configuration: – Minimum processor unit: 0.5 – Assigned processor unit: 1.5  – Maximum processor unit: 3 – Minimum virtual processor: 1 – Assigned virtual processor: 6 – Maximum virtual processor: 8 This LPAR can acquire six processor units if the workload increases and these resources  are available in the CEC. Also, this value is above the limit that is set by the  Maximum  processor unit , which has a value of  3 . But in any case, allocation beyond the limit of the maximum processor unit is something  that is performed at the CEC level, and it cannot be controlled at the PowerHA  SystemMirror level. But it is true that the calculation of available resources can consider what is really being  used in the CEC, and it should not consider the  Maximum processor unit  as an intangible  maximum. The real maximum comes from the value of  Assigned Virtual Processor . PowerHA SystemMirror supports the  uncapped mode , but does not play a direct role in this  support because this mode is used at the CEC level. There is no difference in uncapped  mode compared with the capped mode for PowerHA SystemMirror. 200  IBM PowerHA SystemMirror V7.2.3 for IBM AIX and V7.2.2 for Linux