IT00688: TPC SMAC DU PROVIDES RANDOM SHARE INFORMATION IF THERE IS MORE THAN ONE SHARE SET UP FOR THE SAME FILESET PATH

Refresh Pack 5.2.2 (June 2014) for Tivoli Storage Productivity Center
Fix Pack 5.1.1.5 (July 2014) for Tivoli Storage Productivity Center
Refresh Pack 5.2.3 (August 2014) for Tivoli Storage Productivity Center
Fix Pack 5.2.4 (November 2014) for Tivoli Storage Productivity Center
Fix Pack 5.2.4.1 (December 2014) for Tivoli Storage Productivity Center
Refresh Pack 5.2.5 (March 2015) for Tivoli Storage Productivity Center (withdrawn)
Fix Pack 5.1.1.6 (March 2015) for Tivoli Storage Productivity Center
Fix Pack 5.2.5.1 (April 2015) for Tivoli Storage Productivity Center (withdrawn)
Refresh Pack 5.2.6 (June 2015) for Tivoli Storage Productivity Center
Refresh Pack 5.2.7 (August 2015) for Tivoli Storage Productivity Center
Fix Pack 5.1.1.9 (October 2015) for Tivoli Storage Productivity Center
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)
Fix Pack 5.1.1.12 (October 2016) for Tivoli Storage Productivity Center
Fix Pack 5.1.1.13 (February 2017) for Tivoli Storage Productivity Center
Fix Pack 5.1.1.14 (June 2017) for Tivoli Storage Productivity Center
Fix Pack 5.1.1.15 (Sept 2017) for Tivoli Storage Productivity Center
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)
Fix Pack 5.1.1.8 (July 2015) for Tivoli Storage Productivity Center
Fix Pack 5.2.7.1 (February 2016) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• The problem occurs in case of creating an additional share _adm
  for each productive fileset/share pair in order to mitigate
  permission and access weaknesses in SONAS.
  In TPC SMAC, the DU intends to represent a share but expects
  an 1:1 relationship between fileset and share.
  This works fine for instances created on a portal like SCSA
  or SCO that uses TPC SMAC.
  If afterwards an additional share is created manually for an
  existing fileset pointing to the same path, then the output of
  https://<tpc-host>:9551/SRMAPI/SMAC/DeliveryUnits/xxxxx is
  random:
  It could show the protocol options of the primary share or
  the ones of the additional share.
  Expect behavior would be that a SMAC DU uniquely represents a
  share.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Those using TPC 5.1.1.x and 5.2.0 and 5.2.1.                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * TPC SMAC DU provides random share information if there is    *
  * more than one share set up for the same fileset path         *
  *                                                              *
  * Create an additional share _adm for each productive          *
  * fileset/share pair in order to mitigate permission and       *
  * access weaknesses in SONAS.                                  *
  *                                                              *
  * In TPC SMAC, the DU intends to represent a share but expects *
  * an 1:1 relationship between fileset and share.               *
  *                                                              *
  * This works fine for instances created on a portal like SCSA  *
  * or SCO that uses TPC SMAC.                                   *
  *                                                              *
  * If afterwards an additional share is created manually for an *
  * existing fileset pointing to the same path, then the output  *
  * of https://<tpc-host>:9551/SRMAPI/SMAC/DeliveryUnits/xxxxx   *
  * is random:                                                   *
  * It could show the protocol options of the primary share or   *
  * the ones of the additional share.                            *
  * Expect behaviour would be that a SMAC DU uniquely represents *
  * a share.                                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available.                        *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is targeted for the following maintenance
  package:
  
  | refresh pack | 5.2-TIV-TPC-RP0002 - target June 2014
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future refresh packs or fix packs do not
  represent a formal commitment by IBM. The dates are subject
  to change without notice.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• SMAC
  

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R511 PSY

     UP

• R520 PSY

     UP

• R521 PSY

     UP