IT10159: THE PATH PORT PAIRING FILE ONLY WORKS CORRECTLY IF THE HEX LSS VALUE IS LOWER CASE

Tivoli Storage Productivity Center 5.2.7 (select fixes from group)
IBM Spectrum Control V5.2.8 (December 2015)
IBM Spectrum Control V5.2.9 (February 2016)
IBM Spectrum Control V5.2.10 (May 2016)
IBM Spectrum Control V5.2.10.1 (July 2016)
IBM Spectrum Control V5.2.11 (August 2016)
IBM Spectrum Control V5.2.12 (November 2016)
IBM Spectrum Control V5.2.13 (March 2017)
IBM Spectrum Control V5.2.14 (May 2017)
IBM Spectrum Control V5.2.15 (August 2017)
IBM Spectrum Control V5.2.15.2 (November 2017)
IBM Spectrum Control V5.2.16 (March 2018)
IBM Spectrum Control V5.2.17 (May 2018)

APAR status

• Closed as program error.

Error description

• During establish path TPC-R compares all LSS-LSS pairs in the
  Derby database with what's in the portpairing.csv file, if the
  hex value of the LSS value (hex A - F), is lower case in the LSS
   pair info in the Derby database, but the portpairing.csv has it
   upper case, then no LSS element is returned to the function.
  The result of that is the paths will not be setup properly:
  > 2107.DDYYY-0x90-2107.EEXXX-0xB8 is not equal
  2107.DDYYY-0x90-2107.EEXXX-0xb8
  This problem may also extends to port values having upper case
  hex string in the .csv file
  The workaround is to fill in the HEX LSS value in lower case in
  the portpairing.csv
  

Local fix

• The workaround is to fill in the HEX Lss value in lower case in
  the portpairing.csv
  

Problem summary

• Users that set up the path port pairing between LSS's that have
  hex characters >9 and assign lower case values
  

Problem conclusion

• | fix pack | 5.2.7-TIV-TPC-FP0000 - target 3Q 2015 |
  
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future fix packs do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  
  Customers setting the path port pairing between LSS's that have
  hex characters >9 and assign lower case values will experience a
  problem when trying to establish paths automatically. These
  paths will fail and not be created.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PI44198

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels