Fixes are available
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
in the IBM Spectrum Control probe job for the V7000, we can see the following messages: 2015-11-18 09:27:46.254+0100 HWNEP0001I Successfully persisted 5 rcrelationship instances. 2015-11-18 09:27:46.451+0100 HWNEP0001I Successfully persisted 1 gpfscluster instances. 2015-11-18 09:27:46.481+0100 HWNEP0001I Successfully persisted 2 gpfsnode instances. 2015-11-18 09:27:46.545+0100 HWNEP0001I Successfully persisted 7 filesystem instances. 2015-11-18 09:27:46.614+0100 HWNEP0001I Successfully persisted 7 pool instances. 2015-11-18 09:27:47.086+0100 HWNEP0001I Successfully persisted 50 disk instances. 2015-11-18 09:27:47.456+0100 HWNEP0001I Successfully persisted 97 disk instances. 2015-11-18 09:27:47.600+0100 HWNEP0001I Successfully persisted 7 fileset instances. 2015-11-18 09:27:47.854+0100 HWNEP0001I Successfully persisted 11 export protocol instances. 2015-11-18 09:27:51.257+0100 HWN021719I Perform collection post process tasks for storage system Storwize V7000-2076-XXX-XX_XXX-IBM. The probe is stuck at this step. The post processing takes a lot of time to finish. This is not limited to just SVC or Storwize storage systems. It can affect others. This regression was introduced because of the changes from IT11539 in 5.2.8 (or as a patch provided for 5.2.7). There are no more database handlers since they are not correctly closed. | MDVREGR 5.2-TIV-TPC-RP0008 |
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * TPC 5.2.8 users or 5.2.7 users who have applied a patch for * * APAR IT11539. * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. This problem was introduced in the * * 5.2.8 release due to the fix for APAR IT11539. * **************************************************************** * 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-RP0009 - target March 2016 Fixed in IBM Spectrum Control 5.2.9. http://www-01.ibm.com/support/docview.wss?&uid=swg21320822 The target dates for future refresh packs do not represent a formal commitment by IBM. The dates are subject to change without notice. | MDVREGR 5.2-TIV-TPC-RP0008 |
Temporary fix
Comments
APAR Information
APAR number
IT12593
Reported component name
TPC
Reported component ID
5608TPC00
Reported release
527
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-12-04
Closed date
2016-01-19
Last modified date
2016-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DISK
Fix information
Fixed component name
TPC
Fixed component ID
5608TPC00
Applicable component levels
R528 PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"527","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
22 February 2022