IT07884: ERRORS ENCOUNTERED FOR 1 FABRIC ARE INCLUDED IN THE PROBE JOB LOG FOR ANOTHER FABRIC RESULTING IN BOTH ENDING WITH ERROR

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

• When a fabric probe is run, it kicks off sub-jobs which each
  create their own job log specific to the part of the probe code
  that is being executed.
  For example, the primary probe job log indicates that it
  launches the "collectDataFromSingleFabric" processes for each of
  4 fabrics defined in the probe.
  To illustrate: each of the
  probe_fabric.CollectDataFromSingleFabric*.* log files are
  identified by job IDs xx91, xx92, xx93, xx94.
  xx92 - xx94 each contain info about a single fabric and its
  switches.
  Say that xx91 is for a fabric with 2 switches.  The probe then
  starts the child processes for xx92-xx94 and returns their
  status values.  At the bottom of the log it also lists switches
  in other fabrics which logged a warning.  This fabric probe
  process had no issues running, but ends up being marked as
  warning because of the rolled up warnings from the other
  fabrics.
  TPC should not be including errors in fabric logs, for fabrics
  where the error was not encountered - this results in a false
  failure or false warning status for probes that ran without
  issue.
  RECREATE STEPS:
  Run fabric probes, observe duplicate errors in logs they do not
  belong in.
  ________________________________________________________________
  DB2 Version used for Server:    n/a
  The defect is against component:   5608TPC00
  Server/Manager build/release (TPC):   5.2.3
  
  ________________________________________________________________
  Problem as described by customer:   Fabric probe failures
  Initial customer impact (low/med/high): med
  

Local fix

• Apply fixing PTF when available.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * TPC 5.1.x and 5.2.x users monitoring fabrics                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fix maintenance when available.                        *
  ****************************************************************
  

Problem conclusion

• This logging issue has been corrected so that the status rolls
  up correctly.  The fix for this APAR is targeted for the
  following maintenance package:
  
  | refresh pack | 5.2-TIV-TPC-RP0006 - target June 2015
  
  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.
  

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

• FABRIC
  

Fix information

• Fixed component name

  TPC

• Fixed component ID

  5608TPC00

Applicable component levels

• R523 PSY

     UP

• R520 PSY

     UP

• R511 PSY

     UP

• R525 PSY

     UP