TDS for Software Deployment Analysis Release Notes

TDS for SAnalysisRelease NVersion 1.0March 7, 1999

oftware Deployment

otes

TDS Guide for Software Deployment Analysis 1.0 Release Notes (March 1999)

TDS Guide for Software Deployment Analysis 1.0 Release Notes (March 1999)

TDS for Software Deployment Analysis 1.0 (March 1999)

Copyright Notice

Copyright © 1999 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. Allrights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for TivoliProducts to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted,transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means,electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of TivoliSystems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systemscopyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. Thedocument is not intended for production and is furnished “as is” without warranty of any kind. All warranties onthis document are hereby disclaimed including the warranties of merchantability and fitness for aparticular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subjectto restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, CICS, IBM, MVS,NetView, Tivoli, Tivoli Change Management, Tivoli Decision Support 2.0, Tivoli Management Environment, TME10, OS/2, O/S390, and RS/6000.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks ofMicrosoft Corporation.

Java and all Java-based trademarks or logos are trademarks of Sun Microsystems, Inc.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/OpenCompany Limited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarksof others.

Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply thatthey will be available in all countries in which Tivoli Systems or IBM operates. Any reference to theseproducts, programs, or services is not intended to imply that only Tivoli Systems or IBM products,programs, or services can be used. Subject to Tivoli System’s or IBM’s valid intellectual property or otherlegally protectable right, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunctionwith other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility ofthe user.Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

Tivoli Decision Support Guide Documentation

Each TDS Guide is delivered with on-line documentation. During the installation process, the applicableTDS guide documentation is copied to the Tds\guide docs installation directory on your system.

TDS for Software Deployment Analysis 1.0 Release Notes iv

Table of Contents

Preface .............................................................................................................................. vii

Who Should Read This Book.................................................................................................. vii

Prerequisite Software............................................................................................................. viii

ODBC Drivers ..................................................................................................................................... viii

Software Deployment Analysis Guide Documentation ..........................................................ix

Prerequisite and Related Documentation.................................................................................x

Contacting Customer Support .................................................................................................xi

Introduction ........................................................................................................................1

Tivoli Decision Support for Software Deployment Analysis 1.0 Product Summary............1

Installation..........................................................................................................................2

Requirements ..............................................................................................................................3

Installing the Software Deployment Analysis Guide...............................................................5

Preparing to Work with the Inventory Database..................................................................................... 5

Setting Up an Oracle or Sybase Client................................................................................................ 5

Preparing the Inventory Database........................................................................................................... 6

Setting Up an ODBC Data Source...................................................................................................... 6

After Installing TDS ............................................................................................................................... 6

Configuring the Shared Source File Path............................................................................................ 7Installing and Importing the Software Deployment Analysis Guide .................................................. 8Assigning and Verifying a Data Source............................................................................................ 10Setting the Date Range Parameter in the Cube ................................................................................. 10Building the Cube ............................................................................................................................. 11

Reinstalling a Discovery Guide ...............................................................................................12

Operating Procedures for the Software Deployment Analysis Guide ............................12

Scheduling the Cube Build Task .............................................................................................12

Setting Up Scheduled Cube Builds....................................................................................................... 12

TDS for Software Deployment Analysis 1.0 Release Notes v

Using the Software Deployment Analysis Guide. ..................................................................14

Specifying the Database Logon for Crystal Reports............................................................................. 14

Troubleshooting................................................................................................................ 15

ODBC Driver Problems ...........................................................................................................15

Cube Building ...........................................................................................................................15

Report Problems.......................................................................................................................18

Year 2000 (Y2K) Compliance..................................................................................................19

Inventory Database ............................................................................................................................... 19

Seagate Crystal Reports Version 6 ....................................................................................................... 20

Software Defects, Limitations, and Workarounds ..........................................................21

Defects........................................................................................................................................21

Limitations ................................................................................................................................21

Workarounds ............................................................................................................................22

Dependencies and Compliance Criteria ..........................................................................23

Definition...................................................................................................................................23

Application Dependencies .................................................................................................................... 23

Database Dependencies ........................................................................................................................ 23

Supported Platforms ............................................................................................................................. 24

Supported Languages............................................................................................................................ 24

Functional Definition.......................................................................................................25

Data Sources..............................................................................................................................25

Software Deployment Analysis Database Schema ............................................................................... 25

TABLE: installed_sw_component.................................................................................................... 25TABLE software_filepack ................................................................................................................ 26TABLE software_component ........................................................................................................... 26

Cubes (Tivoli Discovery Administrator) ................................................................................27

Software Distribution Analysis............................................................................................................. 27

Query Used to Build the Cube .......................................................................................................... 27

Parameters Used to Build the Cube ...................................................................................................... 29

Dimensions ....................................................................................................................................... 29Measures ........................................................................................................................................... 33

Check of the Allowed Measures and Dimensions Combination................................................... 33

TDS for Software Deployment Analysis 1.0 Release Notes vi

Topics and Views (Interface) ...................................................................................................35

Related Views and Roles ..........................................................................................................37

New Roles............................................................................................................................................. 40

Report Definitions ....................................................................................................................41

APPENDIX A ...................................................................................................................43

Functions for Calculated Columns: Software Distribution Analysis Cube........................43

QueryName swd_analysis ................................................................................................................ 43

TDS for Software Deployment Analysis 1.0 Release Notes vii

Preface

This document describes the Tivoli Decision Support (TDS) for Software DeploymentAnalysis product. The Software Deployment Analysis Guide is designed to support theTivoli Software Distribution product with a ready-to-use tool in order to spot hiddentrends, improve service levels and make better IT decisions using Tivoli DecisionSupport.

Note: The Tivoli guides as a group are called discovery guides. The TDS for SoftwareDeployment Analysis product is a discovery guide that is also called theSoftware Deployment Analysis Guide.

Who Should Read This Book

This document is intended for the users of the Tivoli Decision Support (TDS) forSoftware Deployment Analysis and anyone responsible for the administration of TivoliDecision Support.

Before using the Software Deployment Analysis Guide, you should be familiar with thefollowing:

• The operating system on your computer

• The basic use of discovery guides and the Tivoli Discovery Interface

To set up the Software Deployment Analysis Guide, your system administrator should befamiliar with the following:

• The Tivoli Discovery Administrator

• The basic use of Crystal Reports

• The basic use of Cognos PowerPlay

TDS for Software Deployment Analysis 1.0 Release Notes viii

• TME 10 Software Distribution 3.6

• TME 10 Inventory 3.6 and the Inventory database

• The Open Database Connectivity (ODBC) for your database

Prerequisite Software

ODBC Drivers

ODBC drivers are provided on the TDS 2.0 CD-ROM.

Database Version Database Version Database VersionDatabaseType ODBC Version ODBC Version ODBC Version

10.X all tier 1 11.0.1.X all tier 1 11.0.3.X all tier 1SybaseINTERSOLV Inc.ODBC 3.01(10.03 client or higher)

INTERSOLV Inc.ODBC 3.01

INTERSOLV Inc.ODBC 3.01

7.2.X all tier 1 7.3.X all tier1OracleMicrosoft ODBC Driver for Oracle2.00.006325

Microsoft ODBC for Oracle2.573.292700

Microsoft ODBC Driver for Oracle2.00.006325

Microsoft ODBC for Oracle2.573.292700

Note: If you experience problems with the INTERSOLV ODBC driver version 3.01for Sybases, contact Tivoli Customer Support, and request the updatedINTERSOLV ODBC driver version 3.01 for Sybase. For more informationabout this issue, please contact Tivoli Customer Support by sending an email [email protected] or by visiting the Tivoli Customer Support web site athttp://www.support.tivoli.com. Please be sure to include your customeridentification information.

mailto:[email protected]

http://www.support.tivoli.com/

TDS for Software Deployment Analysis 1.0 Release Notes ix

Software Deployment Analysis GuideDocumentation

Refer to the following documentation when installing and using the Software DeploymentAnalysis Guide:

Document Description

Location

Tivoli Decision Support(TDS) 2.0 Readme0399.txt

Review this document before installing TDS for Event Management. It contains the latestinformation about the TDS product. This document also describes the features of the TivoliDiscovery Interface that are not documented in version 2.0. These features are found in theTivoli Discovery Interface, and not in the Tivoli Discovery Administrator. The TivoliDecision Support 2.0 User Online Help system provides detailed information andprocedures for using the undocumented features.

Filename on the CD-ROM: d:\Readme0399.txt(where d: is the drive letter for your CD-ROM Drive)

Filename on your system: Tds\Docs\Readme0399.txt

TDS for SoftwareDeployment AnalysisReadme.txt

Provides a description of the product documentation, the initial installation instructions, andthe contact information for Tivoli Customer Support.

Filename on the CD-ROM:d:\Tivoli Decision Support for Software DeploymentAnalysis\NTimage\Readme.txt(where d: is the drive letter for your CD-ROM Drive)

Filename on your system: TDS\Guide docs\Tivoli Decision Support forSoftware Deployment Analysis\Readme.txt

TDS for SoftwareDeployment Analysis ReleaseNotes

Provides copyright, prerequisite, installation procedures, and trouble shooting for theSoftware Deployment Analysis Guide.

Filename on the CD-ROM:d:\Tivoli Decision Support for Software DeploymentAnalysis\NTimage\TDS_SDA_Rel_Notes.pdf(where d: is the drive letter for your CD-ROM Drive)

Filename on your system: TDS\Guide docs\Tivoli Decision Support forSoftware Deployment Analysis\Tds_SDA_Rel_Notes.pdf

Using Decision SupportGuides

Provides an overview of the TDS Guides, cube dimensions and measures, and detailedprocedures for using the TDS Guides.

Filename on your system: TDS\Docs\Pdf\dg.pdf

TDS for Software Deployment Analysis 1.0 Release Notes x

Document Description

Location

Installation Guide Provides installation procedures for TDS and its components in stand-alone and networkmode.

Filename on your system: TDS\Docs\Pdf\install.pdf

Decision Support User’sGuide

Describes TDS features, concepts, and provides procedures for using the Tivoli DiscoveryInterface.

Filename on your system: TDS\Docs\Pdf\user-gd.pdf

Administrator Guide Explains the features of the Tivoli Discovery Administrator.

Filename on your system: TDS\Docs\Pdf\admin-gd.pdf

Other Guides Each Tivoli discovery guide is delivered with online documentation. During theinstallation process for each discovery guide, the applicable discovery guide documentationis copied to the Tds\Guide docs installation directory on your system.

Directory on your system: Tds\Guide docs

Prerequisite and Related Documentation

To use the Tivoli Decision Support for Software Deployment Analysis Guide, you shouldbe familiar with the Tivoli Decision Support library of publications:

• Tivoli Decision Support Installation Guide

• Tivoli Decision Support 2.0 Administrator Guide

• Tivoli Decision Support 2.0 User’s Guide

• Tivoli Decision Support 2.0 Using Decision Support Guides

TDS for Software Deployment Analysis 1.0 Release Notes xi

Contacting Customer Support

To contact Tivoli Customer Support:

Note: Whenever contacting Tivoli Customer Support, please have yourcustomer identification information available.

• Access the Tivoli Customer Support home page athttp://www.support.tivoli.com. After you link to and submit the customerregistration form, you can access many customer support services on theWorld Wide Web. Refer to the Customer Support Handbook for a listing ofTivoli Customer Support services, hours of operation, and contact numbers.This handbook is available online at http://www.support.tivoli.com.

• Send an e-mail to [email protected].

• In the United States, call Tivoli Customer Support at 1-800-TIVOLI-8.

• Outside the United States, refer to your Customer Support Handbook for a listof support numbers in your country. This handbook is available online athttp://www.support.tivoli.com.

To provide comments and suggestions about our documentation:

• We at Tivoli are very interested in hearing from you about your experiencewith Tivoli products, documentation, and services. We welcome yoursuggestions for improvements. If you have comments or suggestions aboutour documentation, please send e-mail to [email protected].






TDS for Software Deployment Analysis 1.0 Release Notes 1

Introduction

Tivoli Decision Support for SoftwareDeployment Analysis 1.0Product Summary

The Tivoli Decision Support for Software Deployment Analysis 1.0 responds to the needfor a strategic view of network activity in terms of the results of distribution actions.This discovery guide provides information about successful and failed attempts to modifythe software contents and supplies the link between the action performed, its result, and thesystem concerned with this action. The Tivoli Discovery Interface presents information ina graphical and a text format and is organized using a set of topic questions and reports.The topic questions for software distribution address success, effectivness, trends, peakvolume, and sources of events.

Tivoli Discovery Interface uses a multidimensional cube built with data added by thedistribution process in the Inventory database and with the data about software andhardware in the configuration repository. Each TDS installation site can control when themultidimensional cube is refreshed.


Installation

The following table lists the sequence of activities required to install the SoftwareDeployment Analysis Guide. The shaded activities are only performed if you are firstinstalling TDS on your system. If TDS is already installed on your system, skip theshaded steps.

How to See section Page

Prerequisite Software viii

Requirements 3

1. Determine the software requirements

Dependencies and Compliance Criteria 23

Set up an Oracle or Sybase Client Setting Up an Oracle or Sybase Client 5

2. Install TDS

3. Install Cognos

4. Install the ODBC drivers

See the TDS Installation Guide documentdescribed in the section Software DeploymentAnalysis Guide Documentation.

Prerequisite and Related Documentation

ix

x

5. Set up an ODBC data source connection Setting Up an ODBC Data Source 6

6. Configure the shared source file path Configuring the Shared Source File Path 7

7. Install the discovery guide

8. Import the discovery guide

Installing and Importing the SoftwareDeployment Analysis Guide

8

9. Assign the ODBC data source

10. Test the connectivity with the data source

Assigning and Verifying a Data Source 10

11. Build the cube Building the Cube 11

12. Schedule the cube build task Scheduling the Cube Build Task 12


Requirements

This section lists the products that are prerequisites for the Software Deployment AnalysisGuide. Refer to the appropriate product documentation for installation procedures.

If you are an administrator, you need:

• Microsoft Windows 95 and Windows NT 3.51 or later

• Tivoli Decision Support 2.0 with the following components:

• Tivoli Discovery Interface

• Tivoli Discover Administrator ( to build cubes)

• Cognos PowerPlay (Administrator)

• Crystal Reports (only required when creating or modifying reports)

• TME 10 Software Distribution 3.6 on your network

• TME 10 Inventory 3.6 on your network

• Access to the Inventory database that contains the software distribution tables

• Oracle or Sybase ODBC driver. For Oracle and Sybase ODBC driver versions, seethe section ODBC Driver Versions.

• A version of Microsoft Access should be available though not required to run TDS

If you are a Crystal Reports user, you need:




• Crystal Reports (only required when creating or modifying reports)


• TME 10 Software Distribution 3.6 on your network

• TME 10 Inventory 3.6 on your network

• Access to the Inventory database that contains the software distribution tables

• Oracle or Sybase ODBC driver. For Oracle and Sybase ODBC driver versions, seethe section ODBC Driver Versions.

If you are a multidimensional view user, you need:




• Cognos PowerPlay (Standard)

• Access to the cube built by the administrator


Installing the Software DeploymentAnalysis Guide

Before using the Software Deployment Analysis Guide, complete the installationprocedures described in the following sections.

Preparing to Work with the Inventory Database

Use the following procedures to create the network identification required by Sybase orOracle to access the Inventory database from the systems running TDS.

Setting Up an Oracle or Sybase Client

Consult your database administrator for the appropriate client configuration. Your systemmust have a valid client configuration for the ODBC connection that TDS uses to accessyour database.


Preparing the Inventory Database

Setting Up an ODBC Data Source

Use the following procedure to connect to an ODBC data source:

1. On the Control Panel, select the ODBC icon

2. Select the System DSN tab.

3. Click Add.

4. Select an ODBC driver, and click Finish.For more information about the ODBC drivers, see the section ODBC Drivers.

5. Enter the appropriate identification and login information for the database.

6. Enter the database qualifier:

• For Sybase, enter tivoli

• For Oracle, enter TIVOLI

Note: Your database qualifier may be different. Contact the databaseadministrator for additional information.

After Installing TDS

After installing TDS, complete the procedures described in this section to finish theSoftware Deployment Analysis Guide installation process.


Configuring the Shared Source File Path

Before using the Tivoli Discovery Administrator or the Tivoli Discovery Interface, theymust be configured to locate certain files (called source files) that are stored on yoursystem (the local system) or on the network. If you installed TDS using the stand-aloneinstallation option, your source files are on your system. For other installations, the sourcefiles usually reside on a network server. Specify the path to the source files when you startthe Tivoli Discovery Administrator for the first time. Use the following procedure to setthe shared source file path:

1. On the View menu, select Options.

The Options dialog box appears.

On the General tab, in the Network box, type the name of the drive (and folder, ifappropriate) that contains the following folders:

• Cubes

• Data

• Reports

2. Click OK.


Installing and Importing the Software DeploymentAnalysis Guide

Use the following procedure to install and import the Software DeploymentAnalysis Guide:

1. Insert the Tivoli Decision Support for Software Deployment Analysis CD-ROM in theCD-ROM drive for your TDS server, and from the Start menu, choose Run.

The Run dialog box appears.

2. In the Run dialog box, type d:\setup.exe (where d: is the drive letter for your CD-ROM drive), and click OK.

The Tivoli Decision Support Discovery Guide Installation window appears.

3. Click on Tivoli Decision Support for Software Deployment Analysis.

The discovery guide files are placed in the following Tds\ installation directories:cubes, models, reports, and install (where Tds\ is the TDS installation directory).

The online documentation is installed in the following director:Tds\Guide docs\Tivoli Decision Support for Software Deployment Analysis

The updated TDS readme is installed in the following directory:Tds\Docs\Readme0399.txt

Note: For more information, see the section Documentation.

4. Start the Tivoli Discovery Administrator.

5. On the Decision Support Guides menu, click Import.

OR

If a discovery guide has not been installed on your system, you are prompted to importan installed discovery guide, and to connect to a data source.


Note: For a step-by-step procedure, see Running the Tivoli DiscoveryAdministrator for the First Time in the Administrator Guide document.

1. A dialog box appears prompting you to import and to install thedecision support guide, select the Tivoli Decision Support for SoftwareDeployment Analysis Guide, click Yes.

2. When prompted to add a data source, click Yes.

3. Select your configured data source.

4. Enter the database userid and password.

5. Enter the database qualifier:

• For Sybase, enter tivoli

• For Oracle, enter TIVOLI

Note: Your database qualifier may be different. Contact thedatabase administrator for additional information.

6. Select Software Deployment Analysis on the Import Decision Support Guides dialogbox, and click OK.

7. Open Microsoft Explorer, and navigate to the Tds\cubes directory (where Tds\is the installation directory path for TDS).


Assigning and Verifying a Data Source

Use the following procedure to assign and verify a data source for the Software DistibutionAnalysis Guide:

1. Using the Tivoli Discovery Administrator, select the Software Distribution Analysiscube.

2. On the Data Sources menu, click Assign Data Sources.

3. Select the data source from the dropdown list.

4. Select the following query, and click OK:

swd_analysis

5. Click the Data Sources folder.

6. Right click on the data source you just assigned, and select Test Connectivity

If the Tivoli Discovery Administrator message dialog box appears with the messageError connecting to Data Source – DataSourceName, click Details to display moreinformation about the connection error. Click OK, and verify the data sourcedefinition, userid, password, and qualifier.

If the connection is successful, the Test Data Source dialog box appears with themessage Connection Successful. Click OK.

Setting the Date Range Parameter in the Cube

The Software Deployment Analysis Guide is designed to work without using the daterange parameter. All calculated periods are relative to the most recent date in the data.


Building the Cube

Schedule cube builds on a regular basis and during periods of decreased database activity.Use the following procedure to build a cube:

1. From the Administrator pane in the Tivoli Discovery Administrator window,double-click Cubes.

2. Right-click on the Software Distribution Analysis cube, and select Build.

The Confirm Cube Build dialog box appears.

3. Click Yes.

TDS connects to your database and retrieves the records specified in your query. Thesize of your data and the network speed affect the time required to retrieve all records.Use the status bar to check the status of the processing.

The Cube Transform Status dialog box appears. Processing messages appear in thedialog box.

4. Review the processing messages for any errors.

If an error generates an error dialog box, review the error, and click OK.

5. Click Close.

6. Start the Tivoli Discovery Interface

7. Use the discovery guide to review the views for each topic (a topic is presented as aquestion).

For more information about how to use the Tivoli Discovery Interface, see the TDSUser’s Guide, and the Using Decision Support Guides documents described in thesection Required Documentation.


Reinstalling a Discovery Guide

To reinstall a discovery guide, you must first uninstall all the discovery guides on yoursystem, and then uninstall TDS. You must now reinstall TDS and then reinstall thediscovery guides.

Operating Procedures for theSoftware Deployment AnalysisGuide

Scheduling the Cube Build Task

You must periodically rebuild the cube to update your data. The build process can bescheduled to build automatically at regular intervals (for example, schedule nightly cubebuilds). Stagger the start times for your cube builds for improved performance.

Setting Up Scheduled Cube Builds

The following procedure uses the Tivoli Discovery Administrator to create a cube buildingschedule and to determine the schedule TaskID. The cube build is then scheduled using theCognos Scheduler. Use the following procedure to define a cube building schedule:

1. Start the Tivoli Discovery Administrator.

2. On the Scheduled Task menu, point to Add, and click Cube Build.

The Add Schedule Wizard appears.


3. Type a name for the schedule you are creating in the Schedule Name box, andclick Next.

4. Continue to click Next until you are prompted for the date range for the schedule.

5. In the Effective from date box, type or select a date that is prior to the current date.

6. Select the To checkbox to display the ending date box.

7. In the ending date box, type or select the date that you entered in the Effective fromdate box, and click Next.

8. Click Finish.

9. In the Tivoli Discovery Administrator pane, click on Scheduled Tasks.

10. In the Properties pane, right click on the scheduled task you created, and click Edit.

The Edit Schedule dialog box appears.

11. On the Task tab, record the schedule Task ID for use in Step 15.

12. Click OK.

13. On the Start menu, under Programs, choose Cognos, and click Scheduler to start theCognos Scheduler.

14. On the Insert menu, click Recurring task.

The Insert Task dialog box appears.

15. On the Identification tab, type the following command string in the File name box:

“<directory path>\edamin.exe” /TaskID=X

(where <directory path> is the installation directory path for TDS and X is the schedule Task ID from Step 11)

Note: Enclose the directory path and the edamin.exe in quotes as shown in thefollowing example: “c:\Program Files\TDS\edamin.exe” /TaskID=1


16. Type a brief description of the cube and the schedule in the Description box.

17. On the Timetable tab, specify the cube building frequency, run time, and duration.

18. Minimize Cognos Scheduler.

Note: Cognos Scheduler must be running for the cube to build at thescheduled time.

Using the Software Deployment AnalysisGuide.

After your system administrator has built the Software Deployment Analysis cube usingthe Tivoli Discovery Administrator, start the Tivoli Discovery Interfaces. Select theSoftware Deployment Analysis Guide, and view a report.

Specifying the Database Logon for Crystal Reports

The first time you run a Crystal Report using the Discovery Interface, you must set thedata source using the Software Deployment Database Logon dialog box. Specify the DSN,the Qualifier, and the Database name and type for the data source you defined.

Enter the following values for the qualifier:

• Sybase database: tivoli

• Oracle database: TIVOLI

Note: Your database qualifier may be different. Contact the databaseadministrator for additional information.


Troubleshooting

ODBC Driver Problems

• If you experience problems with the INTERSOLV ODBC driver version 3.01 forSybases, contact Tivoli Customer Support, and request the updated INTERSOLVODBC driver version 3.01 for Sybase. For more information about this issue, pleasecontact Tivoli Customer Support by sending an email to [email protected] or byvisiting the Tivoli Customer Support web site at http://www.support.tivoli.com. Pleasebe sure to include your customer identification information.

Cube Building

• In the Tivoli Discovery Administrator the following message appears: Error buildingcube. If you click Details on the message dialog box, the following message appears:Error 91 – Error getting query parameters; object variable or with block variable notset.

The data sources have not been assigned to the cube queries. Assign the data sourcesto the queries.

• While using the Discovery Interface, a Cognos PowerPlay report icon appears withthe x symbol (a circle bisected by a diagonal line), and you cannot open the report.What does this indicate?

This symbol indicates that the cube is unavailable. Contact your Tivoli DiscoveryAdministrator, and request that the cube be rebuilt.




• Why does the Tivoli Discovery Administrator report that a cube could not be built?

The cube you are attempting to rebuild is currently in use, and TDS cannot overwritethis cube with the new cube data. Close all copies of the Tivoli Discovery Interfacethat are running. Copy the <CubeName>.mdc file from the Tds\Cubes\Tempdirectory to Tds\cubes directory (where Tds\ is the TDS installation directory),replacing the existing cube.

The queries returned insufficient data to build a cube. Verify your queries.

• You closed all the Tivoli Discovery Interface processes, and the cube still does notbuild.

A copy of Cognos PowerPlay may still be running in the background. This can alsoprevent cube builds from succeeding. Open the Task manager, and look for theprocess pplay.exe. If you find it, end the process, and rebuild the cube.

• Your cube does not automatically build overnight.

For scheduled cube builds to occur, the Cognos Scheduler must be running. StartCognos Scheduler. Review the schedule definitions in Cognos Scheduler and theTivoli Discovery Administrator.


• How are relative dates calculated in a report?

The Date Range parameter for a cube determines the time period that you want toexamine. This parameter uses explicit values, a start date and end date, or a calculatedvalue (for example, the last three months and the last six months). The calculatedvalues are relative to the current date. The current period for a TDS cube is set usingone of the following methods:

• Use the Date Range parameter and the <CubeName>_dt.txt to set the currentperiod as shown in the following table:

If the Date Range parameter is

defined for a query using…

then the resulting date in the <CubeName>_dt.txt1 is the…

Explicit Date Range End Date

Calculated Values Calculated End Date

No Date Range Parameter in the Cube Date the Cube is Built1 where <CubeName> is the name of the cube that is being built

• If you want to use the date in the <CubeName>_dt.txt as the current period,then you must create a new query in the cube model. This query must use the<CubeName>_dt.txt as a local data file. Also, the Set the current period optionmust be set only for this query.

• Use the Date Range parameter, but do not use the <CubeName>_dt.txt . Thisselects only records between the specific start date and end date, and sets thecurrent period to the most recent date in the data.

• Do not use either the Date Range parameter or the <CubeName>_dt.txt. Thisselects all the records, and sets the current period to the most recent date inthe data. (This method is used by the Software Deployment Analysis Guide.)

• Use the <CubeName>_dt.txt, but do not use the Date Range parameter. Thisselects all the records, and sets the current period to the date of the current cubebuild.

• For more information on how to set the current period and select records, seethe TDS Administrator Guide.


Report Problems

• The following error message appears: load_graph_from_powercube.

This indicates that the cube has not been built. Build the cube.

• You tried to open a report, and the Tivoli Discovery Interface gets stuck at the waitcursor.

The Tivoli Discovery Interface may have lost its connection to the Cognos PowerPlaytask. Close the Tivoli Discovery Interface and PowerPlay. Restart the TivoliDiscovery Interface, and your reports should open.

• You opened a report, and it contained no data.

There are several reasons why you might not see any data in a report:

• There may be data in the report, but there is no data in drill down. The reportmay be filtered on a dimension. Look at the dimension bar and check if any ofthe values (especially the date dimension) are drilled down.

• The crystal reports do not have a left margin.

The type of printer attached to a workstation influences the alignment of crystalreports. Try disconnecting the printer and restarting TDS.

• You cannot open a Crystal Report using the Discovery Interface.

You may be addressing the wrong database. Click Options on the SoftwareDeployment Database Logon dialog box to verify that the Data Source is properlydefined by checking the DSN, the Qualifier, and the Database name and type.


Year 2000 (Y2K) Compliance

THIS INFORMATION DOES NOT CONSTITUTE A CERTIFICATION ORWARRANTY, EXPRESS OR IMPLIED, OF ANY KIND.

Inventory Database

• How do you ensure that the database that TDS accesses is Y2K compliant?

To help ensure that TDS continues to select data correctly after January 1, 2000, thedatabase used to store historical data must be Y2K certified. Please contact yoursystem administrator and your database vendor if you have any questions concerningthe Y2K compliance of your database.


Seagate Crystal Reports Version 6

• How do you ensure that Seagate Crystal Reports is Y2K compliant?

Seagate Crystal Reports version 6 is Y2K ready if you download the required patches.Seagate Software considers a product Year 2000 ready if the product performance andfunctionality are unaffected by processing of dates prior to, during and after the Year2000, but only if all products (for example hardware, software and firmware) used withthe product properly exchange accurate date data with it.

Based on testing to date the following versions (in all available languages) of SeagateCrystal Reports, Seagate Crystal Info and Seagate Info are currently Year 2000 ready:1

• Seagate Crystal Reports 62

• Seagate Crystal Reports 7 - Shipped Year 2000 Ready

• Product Name and Version - All Versions, STANDARD & PRO

1 For the compiled report option of Seagate Crystal Reports 6 to be Year 2000 ready, the appropriate versionupdate must be downloaded from the Seagate Software Website.

2 If using a native connection to Xbase (.dbf) database files, a patch must be downloaded from the SeagateSoftware Website. Please refer to the attached FAQ for more information. The official disclosure is postedon Seagate Software’s Year 2000 Readiness page at http://www.seagatesoftware.com/y2k.


Software Defects, Limitations,and Workarounds

Defects

The following is a list of some of the more important software defects. Workarounds areprovided when applicable.

• None.

Limitations

The following is a list of known software limitations for the 3.6.1 release of SoftwareDeployment Analysis. Workarounds are provided when applicable.

• Measures on simple bar graphs appear twice – centered on the graph and over theY axis. On low resolution monitors, the measure names may overlap.

Workaround:

The recommend minimum resolution for your monitor is 800 x 600 pixels.


• <Process_Name.exe> Application Error message dialog box appears with thefollowing message: The instruction at “<memory address>” referenced memory at“<memory address>”. The could not be “read”.

Workaround:

Occasionally, when the cubes are built or their queries are exported, an applicationerror message appears when TDS is used in combination with the SybaseINTERSOLV Inc ODBC driver Version 3.01. This error message can appearfrequently for a time and then suddenly cease to appear. If you experience thisproblem during cube build, wait until the transformation process has completed beforeclicking OK or Cancel on the error message dialog box. By waiting, you allow thecube to finish building. After the build process has completed, click OK on the errormessage dialog box. The Tivoli Discovery Administrator will close. Start the TivoliDiscovery Administrator and continue building any remaining cubes.

Workarounds

The following is a list of workarounds for this release.

• None.


Dependencies and ComplianceCriteria

Definition

Application Dependencies

The Software Deployment Analysis Guide runs using TDS version 2.0

The Software Deployment Analysis Guide requires the following:

• Installation of TME 10 Software Distribution 3.6 on your network

• Installation of TME 10 Inventory 3.6 on your network

Database Dependencies

The Software Deployment Analysis Guide uses ODBC Drivers to communicate with theInventory database.

• Oracle 7.x, 8.x – except 7.2x on AIX

• Sybase 10.x, 11.0.1.x, 11.0.3.x


Supported Platforms

The Tivoli Decision Support Guide for Software Deployment Analysis version 1.0 runs onthe following platforms:

• Windows NT 3.51 and higher

• Windows 95

Supported Languages

This version of TDS for Software Deployment Analysis version 1.0 only supports theEnglish language.


Functional Definition

Note: The term subscribe is used to refer to workstations, personal computers, or othertypes of applicable computing devices.

Data Sources

The data source for the Software Deployment Analysis Guide is the Inventory databaseused by the TME 10 Inventory 3.6 Software Distribution (SWD) product. The SoftwareDeployment Analysis Guide uses the following database tables:

• installed_sw_component

• software_filepack

• software_component

Table Modificationinstalled_sw_component SWD adds a row for each distribution event when a

distribution is completed. If the same file packages isdistributed several times, a new distribution event is addedto the table for each time the file package is distributed.

software_filepack SWD adds a row for each unique file package name.

software_component SWD adds rows for each unique file package name. Thistable also contains an a software inventory of each system.

Software Deployment Analysis Database Schema

In the following there is the structure of the three tables mentioned above:

TABLE: installed_sw_component

Element Name Datatype NULLAccepted

Field Description

HARDWARE_SYSTEM_ID VARCHAR(64) NOT NULLSOFTWARE_COMPONENT_NAME VARCHAR(64) NOT NULLSOFTWARE_COMPONENT_VERSION VARCHAR(16) NOT NULL



Field Description

COMPONENT_LANGUAGE_EDITION VARCHAR(16) NOT NULLINSTALLED_FILEPACK_TIME VARCHAR(32) NOT NULLINSTALLED_FILEPACK_PATH VARCHAR(255) NULLFILEPACK_ACTIVATED INTEGER NULLFILEPACK_ACTIVATION_TIME VARCHAR(32) NULLTME_ADMINISTRATOR_ID VARCHAR(64) NULLACTION_COMPLETED VARCHAR(32) NULL Distributed

Distributed-FailedCommittedCommitted-FailedRemovedRemoved-Failed

TABLE software_filepack


Field Description

SW_FILEPACK_ID VARCHAR(128) NOT NULLFILEPACK_TYPE VARCHAR(64) NOT NULLFP_SOURCEHOST VARCHAR(32) NULL

TABLE software_component


Field Description

SOFTWARE_COMPONENT_NAME VARCHAR(64) NOT NULLSOFTWARE_COMPONENT_VERSION VARCHAR(16) NOT NULLCOMPONENT_LANGUAGE_EDITION VARCHAR(16) NOT NULLSW_FILEPACK_ID VARCHAR(128) NULLMANUFACTURER_ID VARCHAR(64) NULL not usedCOMPONENT_MAJOR_VERSION VARCHAR(16) NULL not usedCOMPONENT_MINOR_VERSION VARCHAR(16) NULL not usedCOMPONENT_REVISION VARCHAR(16) NULL not usedSOFTWARE_COMPONENT_DESCRIPTION VARCHAR(128) NULL not usedSOFTWARE_COMPONENT_PLATFORM_OS VARCHAR(64) NULL not usedSOFTWARE_COMPONENT_PLATFORM_HW VARCHAR(64) NULL not usedSOFTWARE_COMPONENT_FUNCTION VARCHAR(16) NULL not usedSOFTWARE_COMPONENT_SERIAL_NUMB VARCHAR(32) NULL not usedSOFTWARE_COMPONENT_ID_CODE VARCHAR(32) NULL not used


Cubes (Tivoli Discovery Administrator)

Software Distribution Analysis

The Software Distribution Analysis multidimensional cube contains information fromseveral of the Inventory database tables in order to provide metrics about distributionperformance.

Query Used to Build the Cube

The following sql query is used to create the flat file in comma separated value (csv)format. This file will be used to create the multi-dimensional cube.

SELECTMIN(T1.SOFTWARE_COMPONENT_NAME) AS SOFTWARE_COMPONENT_NAME,MIN(T1.SOFTWARE_COMPONENT_VERSION) ASSOFTWARE_COMPONENT_VERSION ,T2.HARDWARE_SYSTEM_ID,T1.SW_FILEPACK_ID,T2.INSTALLED_FILEPACK_TIME,MIN(T2.FILEPACK_ACTIVATED) AS FILEPACK_ACTIVATED,MIN(T2.FILEPACK_ACTIVATION_TIME) AS FILEPACK_ACTIVATION_TIME,T2.ACTION_COMPLETED,MIN(T3.FILEPACK_TYPE) AS FILEPACK_TYPE,MIN(T3.FP_SOURCEHOST) AS FP_SOURCEHOST,MIN(T4.TME_OBJECT_ID) AS TME_OBJECT_ID,MIN(T4.BOOTED_OS_NAME) AS BOOTED_OS_NAME,MIN(T4.BOOTED_OS_VERSION) AS BOOTED_OS_VERSION,MIN(T4.TME_OBJECT_LABEL) AS TME_OBJECT_LABEL,MIN(T5.NETWORK_NODE_NAME) AS NETWORK_NODE_NAME,MIN(T5.NETWORK_NODE_ADDRESS) AS NETWORK_NODE_ADDRESS,MIN(T5.NETWORK_PROTOCOL) AS NETWORK_PROTOCOL,1 AS ITEM_COUNT

FROM?[DB Qualifier].SOFTWARE_COMPONENT T1,?[DB Qualifier].INSTALLED_SW_COMPONENT T2,?[DB Qualifier].SOFTWARE_FILEPACK T3,?[DB Qualifier].COMPUTER_SYSTEM T4,


?[DB Qualifier].NETWORK_NODE T5

WHERET1.SOFTWARE_COMPONENT_NAME = T2.SOFTWARE_COMPONENT_NAME ANDT3.SW_FILEPACK_ID = T1.SW_FILEPACK_ID ANDT2.HARDWARE_SYSTEM_ID = T4.HARDWARE_SYSTEM_ID ANDT5.HARDWARE_SYSTEM_ID = T4.HARDWARE_SYSTEM_ID ANDT5.NETWORK_PROTOCOL = ’TCP’ AND( T5.CONFIG_CHANGE_TYPE in (’INSERT’, ’UPDATE’) ORT5.CONFIG_CHANGE_TYPE IS NULL )

GROUP BYT2.HARDWARE_SYSTEM_ID,T1.SW_FILEPACK_ID,T2.INSTALLED_FILEPACK_TIME,T2.ACTION_COMPLETED

CALCULATED COLUMNS

CC_ALTERNATE_ACTION StringCC_COMPLETION_STATUS StringCC_SUCCESS_VALUE IntegerCC_FAILURE_VALUE IntegerCC_DAY IntegerCC_YYYY IntegerCC_YY IntegerCC_MONTH IntegerCC_HOUR IntegerCC_MINUTE IntegerCC_SECOND IntegerCC_HOUR_MINUTE StringCC_COMPLETE_HOUR StringCC_COMPLETE_DATE StringCC_DAY_OR_NIGHT StringCC_WEEKDAY StringCC_WEEKDAY_NAME StringCC_DAY_AND_TIME StringCC_WEEKDAY_OR_WEEKEND StringCC_FILEPACK_NAME_VERSION StringCC_OSNAME_VERSION StringCC_SUBSCRIBER_NAME_ADDR StringCC_IP_A_NETWORK StringCC_IP_B_NETWORK StringCC_IP_C_NETWORK String

FUNCTIONS

See Appendix A.


Parameters Used to Build the Cube

Parameter name Type Default Values

Day or Night Categorization 7 – 17 (7 AM to 5 PM)

Dimensions

The dimensions defined for the Software Distribution Guide determine the types ofquestions that can be answered by the application.

1. By Date:The time dimension associated with the model.

By Date

Month Week

Day

2. By Day of Week:Permit categorization on Days of the Week.

By Day of Week

CC_WEEKDAY_OR_WEEKEND

CC_WEEKDAY_NAME

CC_COMPLETE_DATE

Special instuctions for model: The values for weekday names should notbe deleted.


3. By Time of Day:Permit categorization by Day and Night and Time of Day

By Time of Day

CC_DAY_OR_NIGHT

CC_HOUR_MINUTE

CC_COMPLETE_HOUR

Special Instuctions: CC_Hour_Minute will have entries for 24 hours in the formatHH:MM [AP]M. These same hours will appear in Daytime or Night definition, theorganization of the hours is based on the Parameter field Day or Night.

4. By Day and Time: Permit Categorization by a concatenated field of date and time

By Day and Time

CC_DAY_AND_TIME

5. By Entire Network: this dimension breaks the IP address down by the 4 parts of the IPaddress. A drill down is provided to relate IP Address to hostname.

By Network Address

CC_IP_A_NETWORK

CC_IP_B_NETWORK

CC_IP_C_NETWORK

NETWORK_NODE_ADDRESS

CC_SUBSCRIBER_NAME_ADDR


6. By Subscriber: This dimension presents the hostname for the subscriber. A drill downis provided to identify the IP Address for the subscriber and the date of the completedsoftware distribution operation.

By Subscriber

TME_OBJECT_LABEL


CC_COMPLETE_DATE

7. By OS: This dimension is provided to relate the OS of the subscriber machine. Thisinformation must be available in the inventory table to be meaningful.

By OS

BOOTED_OS_NAME

CC_OSNAME_VERSION

TME_OBJECT_LABEL


CC_COMPLETE_DATE


8. By Filepackage: This dimension provides information related to the individualsoftware distribution file packages. Drill down is provided to associate filepackversion, subscriber, subscriber IP Address and file pack completion date.

By Filepackage

SOFTWARE_COMPONENT_NAME

CC_FILEPACK_NAME_VERSION

TME_OBJECT_LABEL


CC_COMPLETE_DATE

9. By Action: This dimension presents the actions which software distribution provides asthe alternate actions category and the actual result of the operation.

By Action

CC_ALTERNATE_ACTIONS

ACTION_COMPLETED

10. By Result: This dimension identifies if a software distribution action was a success or afailure.

By Result

CC_COMPLETION_STATUS

ACTION_COMPLETED


Measures

The measures defined for the Discovery Guide for Software Deployment Analysisdetermine key performance indicators using qualitative data.

Measure Name Purpose Calculation

Total number of actions Sum column Column = “ITEM_COUNT”

Number of success actions Sum column Column = “CC_SUCCESS_VALUE”

Number of failure action Sum column Column = “CC_FAILURE_VALUE”

Percent of success Percentage column DPERCENT ( “Number of success

actions” , ”Total number of actions ” )

Percent of failure Percentage column DPERCENT ( “Number of failure

actions” , ”total number of actions” )

Check of the Allowed Measures and Dimensions Combination

The following table lists the measures of the cube and if they are in scope for thedimensions. Measures out of scope for a certain dimension produce invalid information orno data.

Table Legendy = In scope

g = Out of scope

gx = Out of scope, measure allocated to the dimension


Measure

Dimension

Total number ofactions

Number ofsuccess actions

Number offailure actions

Percent ofsuccess

Percent offailure

By Date y y y y y

By Day of Week y y y y y

By Time of Day y y y y y

By Day and Time y y y y y

By Network Address y y y y y

By Subscriber y y y y y

By OS y y y y y

By Filepackage y y y y y

By Action y y y y y

By Result y y y y y


Topics and Views (Interface)

The TDS Discovery Guide for Software Deployment Analysis pose the followingquestions to be answered by data collected from the Inventory configuration repository.

• How effective are file package distributions?

This topic helps you assess and improve your software distribution processbased on the success or failure of each distribute, commit or removeoperation.

View Title Report Title Data Source

Distribution actions that failed by file

package

swd_001.ppr Software Distribution Analysis

File package distribution status swd_002.ppr Software Distribution Analysis

File package status as of last distribution swd_FP_Target(last).rpt Software Deployment Database

• What are the peak distribution periods?

This topic will help you detect patterns in software distribution volume thatare sensitive to the day of the week. This is important for establishing staffingplans and shift schedules for support personnel.


Volume of software distributions by time

period


• What are the software distribution trends?

This topic helps you to spot trends in the volume of software distributions tosubscribers and for file package delivery.



Software distribution history by

subscriber

swd_Target(1day).rpt Software Deployment Database

Success rate for software distribution by

file package


• Which file package distributions have the most problems?

This topic helps to identify problems with file package distributions related tospecific types of systems or operating systems.


File package distribution history by

subscriber

swd_FP_Target(history).rpt Software Deployment Database

Software distribution status related to

subscriber OS


• Which subscribers are receiving distributions?

This topic helps identify software distribution recipients and evaluate thestatus of the distribute, commit and remove operations for the subscribers.


History of file package distributions to

subscribers

swd_Target_FP(history).rpt Software Deployment Database

Software distribution status by network

address


Status of last distribution to subscribers swd_Target_FP(last).rpt Software Deployment Database

Top 100 subscribers with failures swd_006.ppr Software Distribution Analysis


Related Views and RolesFilename View Title View Description Related Views Roles Assigned

swd_001.ppr Distribution actions that

failed by file package

This report helps to target the file package distributionsthat have failures for distribute, remove and commitoperations. Double click on the file package name tosee information about file package version; doubleclick again to see the subscribers the file package wasdistributed to, identifying which systems had failures.

swd_003.ppr Standard

swd_002.ppr File package distribution

status

This report presents the number of success and failuresfor each file package.

swd_FP_Target(last).rpt Standard

swd_FP_Target(last).rpt File package status as of last

distribution

This tabular report lists the last status for file packagedistributions to the subscribers that have received thatfile package. This report can be used to see if thedistributed, committed or removed operation hassuccessfully completed on all workstations. A filter isprovided to select records by file package or by actionperformed. The following are valid actions:"DISTRIBUTED," "DISTRIBUTED-FAILED,""REMOVED," "REMOVED-FAILED,""COMMITTED," "COMMITTED-FAILED."Entry of the filter parameters is case sensitive (i.e. tomatch 10k-dataless you must enter 10k-dataless).

swd_FP_Target(history).rpt Standard

swd_003.ppr Volume of software

distributions by time period

This view displays information about softwaredistribution operations through the last four weeks.This information can be helpful in equalizing softwaredistribution across the network. By selecting either thesuccess or failure measure, you can identify times thatproblems may be occurring within a time period. Usethe 3-D Rotate tool to realign the graph for betterviewing from other angles by right clicking on thegraph and selecting Display Options.

swd_002.ppr

swd_005.ppr

swd_007.ppr

Standard


Filename View Title View Description Related Views Roles Assigned

swd_Target(1day).rpt Software distribution history

by subscriber

This tabular report shows a list of information, groupedby subscriber about distribute, commit or removeoperations for each file package. A filter is provided toselect records relative to a specific day; if no date isentered all records are returned.Entry of the filter parameters is case sensitive (i.e. tomatch 1/21/99 you must enter format Mon dd yyyy likeJan 21 1999).

Standard

swd_004.ppr Success rate for software

distribution by file package

Success rate is the percentage of success for the totalfile package distribution. This view shows the successrate of a distribution process for each action performed(inside each layer level), and for each file package. Bydouble clicking on the file package name, you can getinformation about file package version, subscriber,subscriber IP address and date distribution completed.

swd_001.ppr Standard

swd_FP_Target(history).rpt File package distribution

history by subscriber

This tabular report lists all distribution information inthe database for each subscriber. A filter is provided toselect records by a specific file package or by actionperformed. The following are valid actions:"DISTRIBUTED," "DISTRIBUTED-FAILED,""REMOVED," "REMOVED-FAILED,"COMMITTED," "COMMITTED-FAILED."Entry of the filter parameters is case sensitive (i.e. tomatch 10k-dataless you must enter 10k-dataless).

swd_FP_Target(last).rpt Standard

swd_007.ppr Software distribution status

related to subscriber OS

This report depicts the success or failure of softwaredistributions related to the subscriber operating system.

Standard


Filename View Title View Description Related Views Roles Assigned

swd_Target_FP(history).rpt History of file package

distributions to subscribers

This tabular report identifies the success and failure ofthe file package distribution. A filter is provided toselect a specific subscriber or an action performed. Thefollowing are valid actions: "DISTRIBUTED,""DISTRIBUTED-FAILED," "REMOVED,""REMOVED-FAILED, "COMMITTED,""COMMITTED-FAILED."Entry of the filter parameters is case sensitive (i.e. tomatch 10k-dataless you must enter 10k-dataless).

swd_Target_FP(last).rpt Standard

swd_005.ppr Software distribution status

by network address

This report depicts the success or failure of softwaredistributions related to the subscriber IP address. Aninvalid IP address is displayed as 0.0.0.0.

Standard

swd_Target_FP(last).rpt Status of last distribution to

subscribers

This tabular report lists the status of the last filepackage distribution for this subscriber. This reportcan be used to see if the distributed, committed orremoved operation has successfully completed on aspecific workstation. A filter is provided to selectrecords by subscriber or by action performed. Thefollowing are valid actions: "DISTRIBUTED,""DISTRIBUTED-FAILED," "REMOVED,""REMOVED-FAILED, "COMMITTED,""COMMITTED-FAILED."Entry of the filter parameters is case sensitive (i.e. tomatch 10k-dataless you must enter 10k-dataless).

swd_Target_FP(history).rpt Standard

swd_006.ppr Top 100 subscribers with

failures

This report depicts the failure of software distributionactions related to the top 100 subscribers.

swd_Target_FP(history).rpt

swd_Target(1day).rpt

Standard


New Roles

The standard roles provided by Tivoli Decision Support version 2.0 are set for all PowerPlayreports.


Report Definitions

Filename View Title Rank Report

Type

Period Measure Row Column Other Information

swd_001.ppr Distribution actions thatfailed by file package

Explorer Rolling 4 weeks Number of failureaction

By Action By File package

swd_002.ppr File package distributionstatus

YES Explorer This week to date Total number ofactions

By Result By File package

swd_FP_Target(last).rpt File package status as oflast distribution

CrystalReports

Group by File packageand subscriber, lastoperation per subscriber.Filter file package.

swd_003.ppr Volume of softwaredistributions by timeperiod

Explorer Rolling 4 weeks Total number ofactions

Rolling 4weeks

By day of week

swd_Target(1day).rpt Software distributionhistory by subscriber

CrystalReport

Group by Subscriber, allactivity. Filter by date.

swd_004.ppr Success rate for softwaredistribution by filepackage

YES Explorer Rolling 4 weeks Percent of success By Action By File package

swd_FP_Target(history).rpt File package distributionhistory by subscriber

CrystalReports

Group by File package, alldistributions to eachsubscriber. Filter by filepackage.

swd_007.ppr Software distributionstatus related tosubscriber OS

YES Explorer Rolling 4 weeks Total number ofactions

By Result By OS

swd_Target_FP(history).rpt History of file packagedistributions tosubscribers

CrystalReports

Group by Subscriber, allfile package distributions.Filter by subscriber.

swd_005.ppr Software distributionstatus by networkaddress

YES Explorer Rolling 4 weeks Total number ofactions

By result By IP address


Filename View Title Rank Report

Type

Period Measure Row Column Other Information

swd_Target_FP(last).rpt Status of last distributionto subscribers

CrystalReports

Group by Subscriber andFile package, lastdistribution status. Filterby subscriber.

swd_006.ppr Top 100 subscriberswith failures

YES Explorer Rolling 7 days Number of failureactions

By action By top 100subscribers


APPENDIX A

Functions for Calculated Columns:Software Distribution Analysis Cube

QueryName swd_analysis

Column name: CC_ALTERNATE_ACTIONS

Code

Function CC_ALTERNATE_ACTIONS_Calculate()

if Columns("ACTION_COMPLETED") = "DISTRIBUTED" OR Columns("ACTION_COMPLETED") = "DISTRIBUTED-FAILED" then CC_ALTERNATE_ACTIONS_Calculate = "DISTRIBUTION"end if

if Columns("ACTION_COMPLETED") = "REMOVED" OR Columns("ACTION_COMPLETED") = "REMOVED-FAILED" then CC_ALTERNATE_ACTIONS_Calculate = "REMOVAL"end if

if Columns("ACTION_COMPLETED") = "COMMITTED" then CC_ALTERNATE_ACTIONS_Calculate = "COMMIT"end if

End Function


Column name: CC_COMPLETION_STATUS

Code

Function CC_COMPLETION_STATUS_Calculate()

if Columns("ACTION_COMPLETED") = "DISTRIBUTED" OR Columns("ACTION_COMPLETED") = "REMOVED" OR Columns("ACTION_COMPLETED") = "COMMITTED" then CC_COMPLETION_STATUS_Calculate = "SUCCESS"end if

if Columns("ACTION_COMPLETED") = "DISTRIBUTED-FAILED" OR Columns("ACTION_COMPLETED") = "REMOVED-FAILED" then CC_COMPLETION_STATUS_Calculate = "FAILURE"end if

End Function

Column name: CC_FAILURE_VALUE

Code

Function CC_FAILURE_VALUE_Calculate()

if Columns("CC_COMPLETION_STATUS") = "FAILURE" then CC_FAILURE_VALUE_Calculate = 1else CC_FAILURE_VALUE_Calculate = 0end if

End Function


Column name: CC_SUCCESS_VALUE

Code

Function CC_SUCCESS_VALUE_Calculate()

if Columns("CC_COMPLETION_STATUS") = "SUCCESS" then CC_SUCCESS_VALUE_Calculate = 1else CC_SUCCESS_VALUE_Calculate = 0end if

End Function

Column name: CC_DAY

Code

Function CC_DAY_Calculate()

dim vdate, vday, fr, ls

vdate = Columns("INSTALLED_FILEPACK_TIME") vday= trim(Mid(vdate, 9, 2))

CC_DAY_Calculate = vday

End Function


Column name: CC_MONTH

Code

Function CC_MONTH_Calculate()

dim date, month, m

date = Columns("INSTALLED_FILEPACK_TIME")month = Mid(date, 5, 3)if month = "Jan" then m=1elseif month = "Feb" then m=2elseif month ="Mar" then m=3elseif month = "Apr" then m=4elseif month = "May" then m=5elseif month = "Jun" then m=6elseif month = "Jul" then m=7elseif month = "Aug" then m=8elseif month = "Sep" then m=9elseif month = "Oct" then m = 10elseif month = "Nov" then m=11elseif month = "Dec" then m=12end if

CC_MONTH_Calculate = m

End Function


Column name: CC_YY

Code

Function CC_YY_Calculate()

dim vdate

vdate = Columns("INSTALLED_FILEPACK_TIME")

CC_YY_Calculate = Right(vdate,2)

End Function

Column name: CC_YYYY

Code

Function CC_YYYY_Calculate()

dim vdate

vdate = Columns("INSTALLED_FILEPACK_TIME")

CC_YYYY_Calculate = Right(vdate,4)

End Function


Column name: CC_HOUR

Code

Sub GetDateComponents(sInputDate, sDayOfWeek, sMonth, sDate, sTime, sYear) Dim sWorkDate Dim iColumnNumber

sWorkDate = Trim(sInputDate) sDayOfWeek = "" sMonth = "" sDate = "" sTime = "" sYear = ""

iColumnNumber = InStr(1, sWorkDate, " ") If iColumnNumber < 1 Then Exit Sub sDayOfWeek = Trim(Left(sWorkDate, iColumnNumber)) sWorkDate = Trim(Mid(sWorkDate, iColumnNumber))

iColumnNumber = InStr(1, sWorkDate, " ") If iColumnNumber < 1 Then Exit Sub sMonth = Trim(Left(sWorkDate, iColumnNumber)) sWorkDate = Trim(Mid(sWorkDate, iColumnNumber))

iColumnNumber = InStr(1, sWorkDate, " ") If iColumnNumber < 1 Then Exit Sub sDate = Trim(Left(sWorkDate, iColumnNumber)) sWorkDate = Trim(Mid(sWorkDate, iColumnNumber))

iColumnNumber = InStr(1, sWorkDate, " ") If iColumnNumber < 1 Then Exit Sub sTime = Trim(Left(sWorkDate, iColumnNumber)) sWorkDate = Trim(Mid(sWorkDate, iColumnNumber)) sYear = sWorkDate Exit SubEnd Sub

Function CC_HOUR_Calculate() Dim vdate Dim sDayOfWeek Dim sMonth Dim sDate Dim sTime Dim sYear vdate = Columns("INSTALLED_FILEPACK_TIME") if isnull(vdate) then CC_HOUR_Calculate = 5 else Call GetDateComponents( vdate, sDayOfWeek, sMonth, sDate, sTime, sYear) CC_HOUR_Calculate = Hour(sTime) end ifEnd Function


Column name: CC_MINUTE

Code

Function CC_MINUTE_Calculate() dim vdate dim vx dim vmin

vdate = Columns("INSTALLED_FILEPACK_TIME") vx = Mid(vdate,14,1)

if vx = ":" then vmin = Mid(vdate, 15, 2) else vmin= vx & Mid(vdate, 15, 1) end if

CC_MINUTE_Calculate = vmin

End Function

Column name: CC_SECOND

Code

Function CC_SECOND_Calculate()

dim vdate, vx, vmin

vdate = Columns("INSTALLED_FILEPACK_TIME") vx = Mid(vdate,17,1)

if vx = ":" then vmin = Mid(vdate, 18, 2) else vmin= vx & Mid(vdate, 18, 1) end if

CC_SECOND_Calculate = vmin

End Function


Column name: CC_HOUR_MINUTE

Code

Function CC_HOUR_MINUTE_Calculate()

dim date, HH, MM

HH =Columns("CC_HOUR") MM = Columns("CC_MINUTE")

if HH = "00" then date = "12:00 AM" elseif HH = "12" then date = "12:00 PM" elseif HH < 12 then date = HH & ":00 AM" elseif HH > 12 then date = (HH - 12) & ":00 PM" end if

CC_HOUR_MINUTE_Calculate = date

End Function

Column name: CC_COMPLETE_HOUR

Code

Function CC_COMPLETE_HOUR_Calculate()

dim date, HH, MM, SS

HH =Columns("CC_HOUR") MM = Columns("CC_MINUTE") SS = Columns("CC_SECOND")

if HH = "00" then date = "12:" & MM & ":" & SS & " AM" elseif HH = "12" then date = "12:" & MM & ":" & SS & " PM" elseif HH < 12 then date = HH & ":" & MM & ":" & SS & " AM" elseif HH > 12 then date = (HH - 12) & ":" & MM & ":" & SS & " PM" end if

CC_COMPLETE_HOUR_Calculate = date

End Function


Column name: CC_COMPLETE_DATE

Code

Function CC_COMPLETE_DATE_Calculate()

CC_COMPLETE_DATE_Calculate = Columns("CC_YYYY") & "/" & Columns("CC_MONTH") & "/" & Columns("CC_DAY")

End Function

Column name: CC_DAY_OR_NIGHT

Code

Function CC_DAY_OR_NIGHT_Calculate()

CC_DAY_OR_NIGHT_Calculate = GetDayNight

End Function

Function GetDayNight()

dim DayNight

DayNight = MainEdObj.ResolveCategory(Columns("CC_HOUR"),Parameters("Day ornight"))

If DayNight = "Day" then GetDayNight = "Daytime" Else GetDayNight = "Night" End If

End Function


Column name: CC_WEEKDAY

Code

Function CC_WEEKDAY_Calculate()

CC_WEEKDAY_Calculate = Weekday(Columns("CC_COMPLETE_DATE"))

End Function

Column name: CC_WEEKDAY_NAME

Code

Function CC_WEEKDAY_NAME_Calculate()

CC_WEEKDAY_NAME_Calculate = WeekdayName(Columns("CC_WEEKDAY") )

End Function

Column name: CC_DAY_AND_TIME

Code

Function CC_DAY_AND_TIME_Calculate()

CC_DAY_AND_TIME_Calculate = Columns("CC_WEEKDAY_NAME") & " " & Columns("CC_COMPLETE_HOUR")

End Function


Column name: CC_WEEKDAY_OR_WEEKEND

Code

Function CC_WEEKDAY_OR_WEEKEND_Calculate()

If Columns("CC_WEEKDAY") = 1 then CC_WEEKDAY_OR_WEEKEND_Calculate = "Weekend" ElseIf Columns("CC_WEEKDAY") = 7 then CC_WEEKDAY_OR_WEEKEND_Calculate = "Weekend" Else CC_WEEKDAY_OR_WEEKEND_Calculate = "Business day" End If

End Function

Column name: CC_FILEPACK_NAME_VER

Code

Function CC_FILEPACK_NAME_VERSION_Calculate()

if isNull ( Columns("SOFTWARE_COMPONENT_VERSION")) then CC_FILEPACK_NAME_VERSION_Calculate = Columns("SOFTWARE_COMPONENT_NAME")else CC_FILEPACK_NAME_VERSION_Calculate = Columns("SOFTWARE_COMPONENT_NAME") & " (" & Columns("SOFTWARE_COMPONENT_VERSION") & ")"

end if

End Function


Column name: CC_OSNAME_VERSION

Code

Function CC_OSNAME_VERSION_Calculate()

if isNull ( Columns("BOOTED_OS_VERSION")) then CC_OSNAME_VERSION_Calculate = Columns("BOOTED_OS_NAME")else CC_OSNAME_VERSION_Calculate = Columns("BOOTED_OS_NAME") & " (" &Columns("BOOTED_OS_VERSION") & ")"

end if

End Function

Column name: CC_SUBSCRIBER_NAME_ADDR

Code

Function CC_SUBSCRIBER_NAME_ADDR_Calculate()

if isNull (Columns("NETWORK_NODE_ADDRESS")) then CC_SUBSCRIBER_NAME_ADDR_Calculate = Columns("TME_OBJECT_LABEL")

else CC_SUBSCRIBER_NAME_ADDR_Calculate = Columns("TME_OBJECT_LABEL") & " (" & Columns("NETWORK_NODE_ADDRESS") & ")"end if

End Function


Column name: CC_IP_A_NETWORK

Code

Function CC_IP_A_NETWORK_Calculate()

dim str, p1, p2, p3, sbu1, sb2

str = Columns("NETWORK_NODE_ADDRESS")

if isNull(str) then CC_IP_A_NETWORK_Calculate = NULLelse p1 = InStr(str, ".") if p1 >0 then sub1 = mid(str, p1+1) p2 = InStr(sub1, ".") if p2 >0 then sub2 = mid(sub1, p2+1) p3 = InStr(sub2, ".") if p3 >0 then CC_IP_A_NETWORK_Calculate = GetIP_A_NETWORK else CC_IP_A_NETWORK_Calculate = "0" end if else CC_IP_A_NETWORK_Calculate = "0" end if else CC_IP_A_NETWORK_Calculate = "0" end ifend if

End Function

Function GetIP_A_NETWORK()

Dim NetworkArray

NetworkArray=Split(Columns("NETWORK_NODE_ADDRESS"),".",-1,1)

GetIP_A_NETWORK= NetworkArray(0)

End Function


Column name: CC_IP_B_NETWORK

Code

Function CC_IP_B_NETWORK_Calculate()



if isNull(str) then CC_IP_B_NETWORK_Calculate = NULLelse p1 = InStr(str, ".") if p1 >0 then sub1 = mid(str, p1+1) p2 = InStr(sub1, ".") if p2 >0 then sub2 = mid(sub1, p2+1) p3 = InStr(sub2, ".") if p3 >0 then CC_IP_B_NETWORK_Calculate = GetIP_B_NETWORK else CC_IP_B_NETWORK_Calculate = "0.0" end if else CC_IP_B_NETWORK_Calculate = "0.0" end if else CC_IP_B_NETWORK_Calculate = "0.0" end ifend if

End Function

Function GetIP_B_NETWORK()

Dim NetworkArray


GetIP_B_NETWORK= NetworkArray(0) & "." & NetworkArray(1)

End Function


Column name: CC_IP_C_NETWORK

Code

Function CC_IP_C_NETWORK_Calculate()



if isNull(str) then CC_IP_C_NETWORK_Calculate = NULLelse p1 = InStr(str, ".") if p1 >0 then sub1 = mid(str, p1+1) p2 = InStr(sub1, ".") if p2 >0 then sub2 = mid(sub1, p2+1) p3 = InStr(sub2, ".") if p3 >0 then CC_IP_C_NETWORK_Calculate = GetIP_C_NETWORK else CC_IP_C_NETWORK_Calculate = "0.0.0" end if else CC_IP_C_NETWORK_Calculate = "0.0.0" end if else CC_IP_C_NETWORK_Calculate = "0.0.0" end ifend if

End Function

Function GetIP_C_NETWORK()

Dim NetworkArray


GetIP_C_NETWORK= NetworkArray(0 )& "." & NetworkArray(1) & "." & NetworkArray(2)

End Function

TDS for Software Deployment Analysis Release Notes

Documents

Transcript of TDS for Software Deployment Analysis Release Notes