IC63511: THE ADMINISTRATION CENTER TIVOLI COMMON REPORTING REPORT "TAPE VOLUME CAPACITY ANALYSIS" RETURNS NO DATA

IBM Tivoli Storage Manager V6.1 Fix Pack 3 (6.1.3) Server Downloads

APAR status

• Closed as program error.

Error description

• The Tivoli Common Reporting report "Tape Volume Capacity
  Analysis" returns with no data displayed while a verification
  from the DB2 warehouse database shows that data was collected
  for the indicated report.
  
  This is a known defect within the Tivoli Common Reporting
  scripts.
  Basically when a date field is something out side of the US time
  zones the value is incorrectly converted.
  
  
  Customer/L2 Diagnostics:
  
  Tracing the Tivoli Common Reporting show the following records
  =>
  
  "24/09/09 16:30:15:674 CEST] 00000023 JDBCDriverMan I
  getJndiDSConnection: Unable to get JNDI data source connection;
  java.sql.SQLException: Context:
  tsmCell/nodes/tsmNode/servers/tsmServer, name: ibm/tivoli/tsm:
  First component in name ibm/tivoli/tsm not found.
  [24/09/09 16:30:15:705 CEST] 00000023 reportLogger  1
  com.ibm.tivoli.reporting.reportEngine.impl.BIRTReportLogger
  /TSMReports/TSM_server_tape_volume_capacity.rptdesign NOTE
  ^ModifyQueryCandleDateFromStartTime: start Thu Sep 03 04:00:00
  CEST 2009^n^
  [24/09/09 16:30:15:705 CEST] 00000023 SystemErr     R   RHINO
  USAGE WARNING: Missed Context.javaToJS() conversion:
  Rhino runtime detected object Thu Sep 03 04:00:00 CEST 2009 of
  class java.util.Date where it expected String, Number, Boolean
  or Scriptable instance. Please check your code for missig
  Context.javaToJS() call.
  [24/09/09 16:30:15:721 CEST] 00000023 reportLogger  1
  com.ibm.tivoli.reporting.reportEngine.impl.BIRTReportLogger
  /TSMReports/TSM_server_tape_volume_capacity.rptdesign NOTE
  ^start date... Invalid Date^n^
  [24/09/09 16:30:15:721 CEST] 00000023 reportLogger  1
  com.ibm.tivoli.reporting.reportEngine.impl.BIRTReportLogger
  /TSMReports/TSM_server_tape_volume_capacity.rptdesign NOTE
  ^ModifyQueryCandleBeginDate: date=Invalid Date^n^
  [24/09/09 16:30:15:721 CEST] 00000023 reportLogger  1
  com.ibm.tivoli.reporting.reportEngine.impl.BIRTReportLogger
  /TSMReports/TSM_server_tape_volume_capacity.rptdesign NOTE
  ^startdate=Invalid Date str=NaNNaNNaNNaNNaNNaNNaN pos=199^n^
  [24/09/09 16:30:15:721 CEST] 00000023 reportLogger  1
  com.ibm.tivoli.reporting.reportEngine.impl.BIRTReportLogger
  /TSMReports/TSM_server_tape_volume_capacity.rptdesign NOTE
  ^queryText=with MAXTABLE as
   (select distinct (KSK_TAPE_VOLUME_D."Volume_ID"),
          "WRITETIME" as "WRITETIME",
        "Server_Name"
    from KSK_TAPE_VOLUME_D
    where "Server_Name" = ?
    and "WRITETIME" = 'NaNNaNNaNNaNNaNNaNNaN'
       )
  
  
  Tivoli Storage Manager Versions Affected:
  
  6.1 Reporting and Monitoring
  
  
  Initial Impact: medium
  
  Additional keywords
  zz61  zzrm61 TCR ISC TSM
  

Local fix

• Tape volume information can be found using the Tivoli Storage
  Manager server command QUERY VOLUME or SELECT * FROM VOLUMES  if
  desired
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager                   *
  *                 Version  6.1 users who are running the       *
  *                 Tape Usage Report on a system that is in     *
  *                 a time zone different from the following     *
  *                 time zones: GMT, UT, UTC, EST,               *
  *                 EDT, CST, CDT, MST, MDT, PST, PDT            *
  ****************************************************************
  * PROBLEM DESCRIPTION: See APAR Description                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem will occur when toString method called on
  java.util.Date() object returns
  String with time zone name/abbreviation different than:
  GMT, UT, UTC, EST, EDT, CST, CDT, MST, MDT, PST, PDT
  For Poland the result can be -
  Thu Oct 15 15:39:04 CEST 2009 - which will not
  work, JavaScript Date conversion will fail.
  
  For Eastern Time Zone - Thu Oct 15 09:46:11 EDT 2009 -
  the conversion will work fine.
  

Problem conclusion

• This problem is currently projected to be fixed in level 6.1.3
  Note that this is subject to change at the discretion of IBM.
  
  Affected platforms: AIX, HP-UX, Linux, Sun Solaris, and Windows
  

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

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R61W PSY

     UP