>I discussed this further with Jim Mulder. The z12, where I recently noticed >the 'unassigned' value, introduced 2 GB pages, one of whose consequences is >that LPAR boundaries are rounded up as needed to the nearest 2 GB boundary. If >an image profile specifies any other value, the 'excess' is displayed as >unassigned storage. It can be configured online to the owning LPAR but cannot >be allocated to any other LPAR, hence 'unassigned'.
Thanks for sharing this, Skip. We are in the process of increasing real storage assigned to lpars now that we're on a z13, and sure enough, we had a number of odd storage assignments. That has been rectified now. :-) Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
