There is a recent change that changed the meaning of the LPAR Number in SMF
records:
APAR II13668 said that after z990s, LPARNUM (SMF70LPN) was no longer a
static identifier, but instead is now a system generated number of the
alphabetical location of the LPAR name, and the LPARNUM of an LPAR will
change when you add a new LPAR with a lower-sorted LPAR Name.
But now, IBM has accepted Edward Williams at BMC's suggestion, and in
OA10346 added the new SMF70UPI, User Partition ID, to the RMF 70 record.
Just FYI, you can see some confusing LCPUADDR CPU Address values:
- The PHYSICAL LPAR data has LCPUADDR values that are
totally unexpected: 0,2,5,7,8,10,12,14,16,18,21,23,24,
26,28,30,32,34,37,39,40,42,44,46,48,50,53,55,56,60,62
for the 32 engines! While this has no impact, it does
look strange; IBM says its working as designed.
- Update from Martin Packer, Oct 17, 2005:
It turns out there is an explanation: when LCPUADDR
is displayed as a hex value, the first nybble is the
book number minus one, the second is the CPU number.
So the values above are for book 1 thru book 4, with
hex CPU numbers of 00,02,05,07,08,0A,0C,0E
Hope this helps.
Barry Merrill
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
