Re: LPAR IDs

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

When you create the LPAR you can assign any ID you would like as long as 
it's not already in use.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/19/2011 3:09 PM, rob@xxxxxxxxx wrote:
> We have a partition number higher than the partition count.  We deleted a
> partition and it kept the same number.  To do so otherwise would screw up
> the keys for some canned software which uses partition number for the key.
>
> One time we upgraded a CEC.  Perhaps we didn't do something right.  But I
> ended up rekeying the configuration for multiple lpars.  Luckily I was
> documented to the gills and really had no problem.  We did a phantom lpar
> and deleted it after creating one after it just to keep the right
> partition number on that latter one.
>
>
> Rob Berendt
> -- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 
> Ship to: Dock 108 6928N 400E Kendallville, IN 46755 
> http://www.dekko.com From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx> 
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 
> Date: 09/19/2011 03:56 PM Subject: LPAR IDs Sent by: 
> midrange-l-bounces@xxxxxxxxxxxx Saw an interesting screen shot just 
> now. If you're familiar with Touchtone products, you probably already 
> know that our authorization codes are issued for specific LPARs of 
> specific systems, and that as a convenience, our WRKxxxxAUT 
> authorization code installer utilities display the model, serial, 
> number of LPARs, and the LPAR ID (in hex) of the partition in which 
> they are being run. So this terminal session screen shot showed the 
> WRKVIEWINF screen for QuestView, and showed "LPARs: 31 Current 
> partition: 21" Given that the current partition is definitely 
> displayed in hex, and (so far as I can recall; it's been many years 
> since I've looked at the code, but we've never seen a digit higher 
> than 9 in it) the number of LPARs is displayed in decimal, that would 
> give a partition ID that's higher than the partition count. Anybody 
> have a clue about how or why that would happen? Are systems allowed to 
> have breaks in the sequence of LPAR IDs? -- JHHL