IT11270: WHEN ESTABLISHING REVERSE PATHS LSS MAPPINGS ARE TRANSPOSED BETWEEN THE SOURCE AND THE TARGET.

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

• When establishing paths for sessions the forward and the reverse
  paths can both be created. If the code is establishing the
  paths in the forward direction the path defined in the port
  pairing csv file will be read properly. However, if a reverse
  path is requested the product transposes the LSS's and therefore
   will not pick up a matching mapping from the portPairing.csv
  file. Instead the default path matching mechanism will be used
  which will default to an existing path between the LSS-LSS
  pairing or if none are defined will use a previously defined
  mapping from the TPC-R database, if one was never defined create
   a path between the LSS's with the first available set in the
  list.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of TPC_R whom define paths via the portPairing.csv     *
  * file with LSS to LSS pairings that are not the same source   *
  * and target ID                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * | fix pack | 5.2.8-TIV-TPC-FP0000 - target 4Q 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.                                                      *
  *                                                              *
  * The get ports code when doing a reverse path establisth will *
  * look up the LSS ID with the Target Box Source LSS and the    *
  * Source Box Target LSS. The LSS's are transposed and          *
  * incorrect, therefore since the pairing is not defined in the *
  * portPairing.csv no preferences are set. This causes the      *
  * product to react as if there is no port paring file defined  *
  * for this LSS-LSS paring and use the pre-defined port pairing *
  * or attempt to choose a new port pairing rather than using    *
  * the one defined in the file.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Define port pairing in reverse direction via the paths panel *
  * if feasable                                                  *
  ****************************************************************
  

Problem conclusion

• The getPort will now call the correct order for LSS-LSS
  portsPairing so that the value in the portPairing.csv will be
  used.
  

Temporary fix

• Add a new line that also has transposed the LSS's for the paths
  in the portPairing properties file. e.g.
  
  2107.Source:0xb1:2107.Target:0xd1
  And
  2107.Source:0xd1:2107.Target:0xb1
  
  This would create the correct path pairing in the reverse,
  however if you are starting a session also with pairs from D1-B1
  in the forward direction this would also establish that path
  pairing.. This apar only affects the reversee path namely
  2107.Target:0xd1 to  2107.Source:0xb1. The forward path should
  already work -- e.g.  2107.Source:0xb1 --> 2107.Target:0xd1
  

Comments

APAR Information

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

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

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R520 PSY

     UP