IT33730: PERFORMANCE MONITORS FAIL FOR SOME DEVICES BECAUSE THEIR SCHEDULES HAD NOT BEEN MIGRATED TO NEW MT SCHEDULER.

APAR status

• Closed as program error.

Error description

• Performance monitors fail to run because the job definitions
  for them were not migrated to new MT Scheduler. This is similar
  to APAR IT33241 but is a different variation in that it?s
  related to internal ID vs Device name.
  
  When migrations fail,
  messages of the following type are logged in the following
  logs: traceDataCollectorManager_*.log and
  traceDataCollectorManager_errors_*.log
  
  Example of errors
  seen:
  2020-07-15 09:09:07.421-0400 [pool-551975-thread-1]
  [MigrateToNewScheduler.setScheduleManagedByCollector] [ERROR]
  Failed to mark schedule entry to use MT scheduler.
  1163330
  2020-07-15 09:09:33.687-0400 [pool-551977-thread-1]
  [MigrateToNewScheduler.setScheduleManagedByCollector] [ERROR]
  Failed to mark schedule entry to use MT scheduler.
  690187
  2020-07-15 09:09:50.040-0400 [pool-551979-thread-1]
  [MigrateToNewScheduler.setScheduleManagedByCollector] [ERROR]
  Failed to mark schedule entry to use MT scheduler.
  1099242
  2020-07-15 09:10:25.245-0400 [pool-551984-thread-1]
  [MigrateToNewScheduler.setScheduleManagedByCollector] [ERROR]
  Failed to mark schedule entry to use MT scheduler.
  1132317
  
  
  The defect is against component: Storage
  Insights
  Server/Manager build/release (SI): 5.3.7
  Problem as
  described by customer: Storage Insights not collecting
  performance data
  Initial customer impact (low/med/high): high
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Storage Insights users collecting performance data for   *
  * storage devices                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IBM Storage Insights was not collecting performance data.    *
  *                                                              *
  * The performance monitors were failing to run because the     *
  * job definitions for them were not migrated to the new MT     *
  * Scheduler.                                                   *
  * This is similar to APAR IT33241 but is a different variation *
  *                                                              *
  * in that it is related to internal ID vs Device name.         *
  *                                                              *
  * When migrations fail, there are messages logged in the       *
  * following logs:                                              *
  *                                                              *
  * traceDataCollectorManager_*.log                              *
  * and                                                          *
  * traceDataCollectorManager_errors_*.log                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is targeted for the following release:
  
  IBM Storage Insights 4Q20   [ 5.4.1-IBM-SC ]
  
  ( release target 4Q 2020 / November )
  
  The target dates for future releases 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:

Fix information

• Fixed component name

  STORAGE INSIGHT

• Fixed component ID

  5608TPCSI

Applicable component levels