Symptom 6: Displayed name of an LPAR in the OSA LPARs workspace does not map to the correct data

When users set up their OSA LPARs, they commonly rely on two sources of information:

• zSeries Partition Identification in an MCSS Processor, written by John Hughes of the Advanced Technical Support IBM® Washington Systems Center and available at this Web address: http://www-03.ibm.com/support/techdocs/atsmastr.nsf/5cb5ed706d254a8186256c71006d2e0a/034714811332437286256e770064f628/$FILE/MCSSPartitions.pdf
• The IBM zEnterprise® 196 Technical Guide redbook ( SG24-7833), available at http://www.redbooks.ibm.com/redbooks/pdfs/sg247833.pdf

However, the recommendations in these guides are inconsistent.

The Mainframe Networks product relies on two sources of information to calculate the values that appear in the OSA LPARs workspace:

• Data that is returned from a DIAGNOSE 204 command return the LPAR name and online status of each LPAR. Data for user-defined OSA LPARs are returned with UPID in the range of x'00' to x'3F' , resulting in 64 valid possible designations for OSA LPARS.
• Data that is received from z/OS® SNMP Agent returns LPAR performance data along with two values which are used to correlate the data that is returned from the DIAGNOSE command.
  • Logical Channel Subsystem ID value between x'00' - X'03'
  • Multiple image facility (MIF) in the range of x'01' - x'0F'

To properly report LPAR performance metrics in the OMEGAMON® for Mainframe Networks product, follow the guidelines outlined in the OSA LPAR designations recommended in the zSeries Partition Identification in an MCSS Processor. Specifically this document states the following when defining a UPID:

The first digit of the Logical Partition Identifier should be the CSSID and the 
  second digit of the Logical Partition Identifier be the MIF Image ID. 

Do not use these four designations because they do not map correctly to SNMP data when that data is returned:

• x'00'
• x'10'
• x'20'
• x'30'