Modifying V5.5 Operational Reporting for use with Tivoli Storage Manager V6 and V7 servers

Product documentation


Abstract

This document assists customers who want to use the Tivoli® Storage Manager V5.5 Operational Reporting feature with Tivoli Storage Manager V6 and V7 servers, before making the transition to the reporting and monitoring feature that was introduced in V6. The instructions for configuring V5.5 Operational Reporting to work with V6 and V7 servers are provided as is, and no additional support will be provided by IBM. See the full document for restrictions and instructions.

Content

Rules of use

  • The instructions for configuring V5.5 Operational Reporting to work with V6 or V7 servers are provided as is. No additional support will be provided by IBM.
  • Follow the instructions to modify the V5.5 Operational Reporting feature to make the default reports and monitors work with V6.1 and V6.2 servers.
  • You may run both the V5.5 Operational Reporting feature and the V6 or V7 reporting and monitoring feature at the same time. However, you must install and run the features on different systems.
  • The V5.5 Operational Reporting feature cannot be installed on the same system as the V6 or V7 Management Console.
  • Apply the latest fix pack for the Tivoli Storage Manager V6 or V7 server to ensure that any available fixes are in place for SELECT statements or output.

Back to top

Background information

Tivoli Storage Manager V6 introduces the reporting and monitoring feature, which has new, extensive reporting functions that replace Tivoli Storage Manager V5.5 Operational Reporting. The Tivoli Storage Manager V6 reporting and monitoring feature collects historical Tivoli Storage Manager data, so a separate server is required to run the feature. The Tivoli Storage Manager V6 reporting and monitoring feature supports reporting for both Tivoli Storage Manager V5.5 and V6 servers. For details, see Installing the reporting and monitoring feature.

Also introduced with Tivoli Storage Manager V6 is the change from a proprietary Tivoli Storage Manager database to a DB2® database. Because the DB2 program is the database manager, Tivoli Storage Manager V6 introduces fundamental changes to the database and recovery log architecture. The Tivoli Storage Manager database schema and the SELECT syntax also changed, both of which are used by Tivoli Storage Manager Operational Reporting. For information about the V6 changes, see Server database updates overview and Changes to the SELECT command.

Tivoli Storage Manager V5.5 Operational Reporting is part of the Tivoli Storage Manager Management Console for V5.5 servers, which runs only on Windows® systems. V5.5 Operational Reporting is not supported and not included with Tivoli Storage Manager V6. If a Tivoli Storage Manager V5.5 server on a Windows system is upgraded to Tivoli Storage Manager V6, the Tivoli Storage Manager V6 Management Console is installed without the Operational Reporting feature.

Without modification, the V5.5 Operational Reporting feature does not work with V6 or V7 servers. The default Custom Summary report sections in reports and monitors fail for a Tivoli Storage Manager V6 server, typically with error messages that cite syntax errors or references to columns that do not exist in the V6 server database. Customized reports might also fail.

Back to top

Preparation

To modify Tivoli Storage Manager V5.5 Operational Reporting to work with a Tivoli Storage Manager V6 or V7 server, the Tivoli Storage Manager V5.5 Management Console, which includes Operational Reporting, must be installed on a separate physical or virtual Windows device.
Important: After you make the changes that are described in this document, the reports and monitors that you modify will not work with a V5 server.
  1. If you do not already have the Tivoli Storage Manager V5.5 Management Console installed on a separate physical or virtual Windows device, download the program and install it.
    1. Go to the FTP site for V5.5 downloads for Windows systems: ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/server/v5r5/WIN/LATEST
    2. Download the file for the Tivoli Storage Manager V5.5 Management Console, which has a name like 5.5.x.x-TIV-TSMCON-Windows.exe, where the x.x are numbers that indicate the fix level.
    3. Run the file that you downloaded to install the Tivoli Storage Manager V5.5 Management Console.
  2. Configure Tivoli Storage Manager V5.5 Operational Reporting according to the instructions at this link: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmcw.doc/anrwgd55668.htm
  3. Place the attached default_rep_eng_TSM6or7.xml file in:
    C:\Program Files\Tivoli\TSM\console\default_rep_eng_TSM6or7.xml
  4. Place the attached default_mon_eng_TSM6or7.xml file for modification of monitors in:
    C:\Program Files\Tivoli\TSM\console\default_mon_eng_TSM6or7.xml
  5. Optional: Use the updated templates as the default.

    The custom summary section included in reports and monitors are based on the following Tivoli Storage Manager V5 template files by default:

     C:\Program Files\Tivoli\TSM\console\default_rep_eng.xml
     C:\Program Files\Tivoli\TSM\console\default_mon_eng.xml
    Note: Unless a different template has been specified for existing reports and monitors they will be using the default TSM version 5 template files so please consider that before updating them.

    If you want to use the attached updated templates as the defaults, complete the following steps:

    1. Rename the following two default files to add _TSM5 to the file name:
      • Rename default_rep_eng.xml to default_rep_eng_TSM5.xml.
      • Rename default_mon_eng.xml to default_mon_eng_TSM5.xml.
    2. Rename the new files to the default names and place them in the C:\Program Files\Tivoli\TSM\console directory:
      • Rename default_rep_eng_TSM6or7.xml to default_rep_eng.xml.
      • Rename default_mon_eng_TSM6or7.xml to default_mon_eng.xml.
      Note: Any new reports or monitors will automatically use the new templates since they are now the defaults.
  6. Specifying a template to use with a report or monitor. To have a report or monitor use the template file, complete the following steps:
    1. Right-click a report or monitor and click Properties.
    2. Click Custom Summary.
    3. Click Settings.
    4. Select the template file that you want to use and click OK.

Back to top

Report template updates

The attached report template file default_rep_eng_TSM6or7.xml includes the following updates:

LDBB from db where cast((current_timestamp-last_backup_date)hours as decimal)<%s Modified select statement:
select substr(char(last_backup_date), 1, 16) as LDBB from db 
where TIMESTAMPDIFF (8,CHAR(current_timestamp-last_backup_date ))<%s
PCTUTILIZED (%Database Utilization)
Original select statement:
select pct_utilized from db
Suggested modified select statement:
select sum(100-(free_space_mb*100) / tot_file_system_mb) as PCT_UTILIZED 
from db

The PCT_UTILIZED variable has no direct equivalent in Tivoli Storage Manager V6 or V7 servers. To monitor the usage of database space, the ratio of FREE_SPACE_MB to TOT_FILE_SYSTEM_MB can be used to give similar results. The suggested select statement gives the percent utilized of the space available to the database.

To be automatically warned when the space available to the database is nearly full, activate a notification rule to receive a message if this value reaches a high percentage, for example 85%.

CACHE_PCT (Database Cache Hit Ratio)
Original select statement:
select CACHE_HIT_PCT as CACHE_PCT from DB
Modified select statement:
select BUFF_HIT_RATIO as CACHE_PCT from DB
MAX_PCT_UTILIZED (% Maximum Recovery Log Utilization)
Original select statement:
select max_pct_utilized from log
You can either delete this Select Variable, or change it to report on the file system where the active log is located. A suggested modified select statement:
select cast(sum(used_space_mb *100 / total_space_MB) as decimal(3,1)) 
as MAX_PCT_UTILIZED from log
The suggested select statement reports the percent utilized of the file system where the active log resides. The number is important because problems occur if the file system where the active log resides fills up.
RESET_BUFFPOOL
Original select statement:
reset bufpool
Delete this Select Variable. Tivoli Storage Manager servers at V6.1 and later do not reset the buffer pool.
TMS (Number of tape mounts)
Original select statement:
select count(*) as TMS from summary
where activity='TAPE MOUNT' and cast((current_timestamp-start_time)hours 
as decimal)<%s
Modified select statement:
select count(*) as TMS from summary where activity='TAPE MOUNT' 
and TIMESTAMPDIFF (8,CHAR(current_timestamp-start_time ))<%s
MTM (Total number of minutes tape were mounted)
Original select statement:
select (sum(end_time-start_time))minutes as MTM from summary 
where activity='TAPE MOUNT' and 
cast((current_timestamp-start_time)hours as decimal)<%s
Modified select statement:
select (sum(TIMESTAMPDIFF(4,end_time-start_time))) as MTM from summary 
where activity='TAPE MOUNT' and 
TIMESTAMPDIFF (8,CHAR(current_timestamp-start_time )) <%s

Back to top

Monitor template updates

The attached monitor template file default_mon_eng_TSM6or7.xml includes the following updates:

PCTUTILIZED (%Database Utilization)
Original select statement:
select pct_utilized from db
Suggested modified select statement:
select sum(100-(free_space_mb*100) / tot_file_system_mb) as PCT_UTILIZED 
from db

The PCT_UTILIZED variable has no direct equivalent in Tivoli Storage Manager V6 servers. To monitor the usage of database space, the ratio of FREE_SPACE_MB to TOT_FILE_SYSTEM_MB can be used to give similar results. The suggested select statement gives the percent utilized of the space available to the database.

MAX_PCT_UTILIZED (% Maximum Recovery Log Utilization)
Original select statement:
select max_pct_utilized from log
You can either delete this Select Variable, or change it to report on the file system where the active log is located. A suggested modified select statement:
select cast(sum(used_space_mb *100 / total_space_MB) as decimal(3,1)) 
as MAX_PCT_UTILIZED from log
The suggested select statement reports the percent utilized of the file system where the active log resides. The number is important because problems occur if the file system where the active log resides fills up.

Back to top

Modifying custom reports

If custom reports have been created in the Operational Reporting feature, verify that the syntax of custom select statements is correct for V6 or V7 servers. Review the information in the following document to learn about the changes that were made to the Tivoli Storage Manager server SELECT command between V5.5 and V6: Changes to the SELECT command.

For additions and corrections to this information about the SELECT command, see the technote: http://www.ibm.com/support/docview.wss?uid=swg21380830

Back to top

default_mon_eng_TSM6or7.xmldefault_mon_eng_TSM6or7.xml
default_rep_eng_TSM6or7.xmldefault_rep_eng_TSM6or7.xml


Related information

Download operational reporting executable file
Using IBM Tivoli Storage Manager Operational Reporting

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager
Server

Software version:

6.1, 6.2, 6.3

Operating system(s):

Platform Independent

Software edition:

Edition Independent

Reference #:

7019794

Modified date:

2011-04-29

Translate my page

Machine Translation

Content navigation