IC99392: DIFFERENT TPC COMPONENTS REFERENCE DIFFERENT JDBC DRIVER FILES IN DIFFERENT LOCATIONS.

Refresh Pack 5.2.2 (June 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.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
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)
Fix Pack 5.2.7.1 (February 2016) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• Currently, the various TPC components access the DB2-based TPCDB
  database repository using different driver files in different
  locations.  Certain components bundle the db2jcc.jar driver file
  within the TPC installation directories while others refer to
  the OS classpath which should be configured to the db2jcc.jar
  file located with the DB2 instance.
  Situations beyond the control of TPC software have exposed that
  its sometimes possible for the OS classpath to not get updated
  when DB2 is upgraded and/or reinstalled.  For example the TPC
  Data Server process sets a dynamic classpath variable when
  started and if this hard-coded variable points to a location
  that no longer exists, the TPC Data Server process will fail to
  start.
  Troubleshooting this current, mixed configuration is not a
  straightforward process and typically requires product
  development to be engaged.  This APAR changes the TPC design to
  refer to one, centralized DB2 JDBC driver.  This simplifies
  diagnosis of database communication related problems and reduces
  redundancy.
  RECREATE STEPS:
  Varied
  ________________________________________________________________
  DB2 Version used for Server:    10.1
  The defect is against component:   5608TPC00
  Server/Manager build/release (TPC):   5.2.0.0
  Agent build/release (TPC):    N/A
  Server/Manager (OS):     N/A
  Agent (OS):       N/A
  ________________________________________________________________
  Problem as described by customer:   Data server won't start
  after DB2 upgrade
  Initial customer impact (low/med/high): med
  

Local fix

• Varied
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * TPC 5.2.0 users                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available.                        *
  ****************************************************************
  

Problem conclusion

• A common JDBC driver will be used in TPC.  The fix for this APAR
  is targeted for the following maintenance package:
  
  | refresh pack | 5.2-TIV-TPC-RP0001 - target March 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

• DB
  

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R520 PSY

     UP