ShowCase Analyzer 7.01 README

Contents

• Introduction
• Limitations
  
• Known Issues

Introduction

This Readme lists known issues and limitations found in ShowCase Analyzer 7.01. Known issues will be resolved in a future ShowCase Analyzer 7.01 patch. Limitations cannot be resolved.

You can find additional release notes in the ShowCase Analyzer 7.01 Guide, Chapter 2. For the latest ShowCase Analyzer documentation, refer to the Documentation web page, accessible through the SPSS Support site.

V5R4 is supported with Analyzer patch 7.01.250 and higher. Required Java Group PTF is SF99291. (*Added 9/19/06.)

[ top ]

Limitations

ShowCase Analyzer 7.01 has the following limitations. These issues will not be resolved in a future patch.

• Microsoft Internet Explorer 7.x

  Showcase Analyzer does not currently support Microsoft Internet Explorer 7.x

• ShowCase Data Models (SDMs) and ShowCase Suite 7.1

  The use of SDMs in ShowCase Analyzer 7.01 is not supported when used with ShowCase Suite 7.1.

• Essbase filters, alias tables, and calc scripts are not updated

  Essbase connections are cached. To apply Essbase user and database changes (Essbase filters, alias tables, and calc scripts, for example) you must clear the cache using one of the following methods:

  • After making changes in the Essbase Application Manager, go to Security | Connections and logoff all users.

  • Restart the Analyzer server.

• Personal variables

  Personal variables cannot be shared amongst different users. For example, when user A creates a set of personal variables, user B is unable to see or work with user A's personal variables.

• Unicode Compliance

  ShowCase Analyzer 7.01 is Unicode compliant with the notes listed below. Analyzer 7.01 assumes all data is normalized to the same normal form. Data stored in different normal forms may cause unpredictable results.

  • ShowCase Essbase databases are supported only when using the default Essbase locale. All Essbase 6.51 databases are supported because they use the default locale. Essbase 7.1 supports multiple locales; only the default locale is supported.

    Note: Some Essbase 7.1 locales are Unicode locales (Unicode databases). Since non-default locales are not supported, and a Unicode locale is never the default, Unicode databases are not supported.

  • The Analyzer.properties file must be in Latin-1 format (the default setting). Any character not found in the Latin-1 character set can be inserted using Unicode escape sequences.

  • The QueryEngine.cfg file is only supported when using the default codepage. Unicode escape sequences are not supported. Unicode characters are also not supported. Customers who do not use the Latin-1 character set may be limited to ASCII characters.

• Appearance and formatting differences after migration from 4.5 to 7.01

  In addition to the migration limitations outlined in the ShowCase Analyzer 7.01 Guide, users may experience the following report changes after migrating from 4.5 to 7.01.

  • Ordering and layout
    Migrated items may be positioned differently in reports. For example, when relative positioning is specified in button ordering, Analyzer ignores absolute positioning. Since all buttons are positioned to the right, Analyzer displays buttons in the order in which they are defined.

  • Database formatting
    Database formatting will be removed and center-justified formatting will be used. Scale factor is no longer supported.

  • Button labels
    Analyzer ignores button label information for subscription controller buttons.

  • Controls appearance
    After migrating to Analyzer 7.01, you may notice small differences in the appearance of controls. For example, version 7.01 may place text beside an image rather than below it.

  • Missing combo box content
    Combo boxes containing dynamic content from an inaccessible data source are not migrated. If you have not yet migrated, fix the view or data source. If you have already migrated, re-link the data source.

  • Extra components visible, or buttons hidden
    ShowCase Analyzer 7.01 displays different z-ordering than previous versions. Z-ordering is a scheme that determines which components are in the top, most visible position. You may see components that were part of the original form but are now hidden beneath other components, or you may notice that some buttons are missing/hidden.
    
    You can remove unwanted components or show hidden buttons. To display hidden "extra" components:

    • Select Tools | Design Report.
    • Open Tree View.
    • Compare the number of tree nodes to the number of controls you see.
    • Move controls down into the tree; move the control(s) to a position that will be visible in the report.

  • Missing filters panel
    After migrating a view, the filters panel is no longer displayed by default. The "show filter panel" preference is not migrated. To fix, select Tools | User Preferences and select Look & Feel. Ensure that the Filter Panel box in the display section is selected.

• Calculation-value differences after migration from 4.5 to 7.01

  The values of calculations containing missing data in views migrated from 4.5 to 7.01 differ from 4.5 calculation values, even when the missing value option (Include/Exclude) remains unchanged.

• French, German, & Japanese launch page
  
  By default, the English launch page is displayed.
  
  To display the French launch page, enter the appropriate URL in the following format:
  http://iseriesname:port/index_fr.html
  For example: http://prodserver:12345/index_fr.html
  
  To display the German launch page, enter the appropriate URL in the following format:
  http://iseriesname:port/index_de.html
  For example: http://prodserver:12345/index_de.html
  
  To display the Japanese launch page, enter the appropriate URL in the following format:
  http://iseriesname:port/index_ja.html
  For example: http://prodserver:12345/index_ja.html

• Licensing error
  
  Simultaneous connection attempts may result in a licensing error during log in. If this should occur, attempt to log in again. The next log in attempt should be successful if no other users attempt to connect at the same time.

• Percent of member

  The percent of member calculation definition dialog does not display the correct "opposite member" for the calculation.

  When creating a percent of member calculation, you select the member to be used from the list in the "opposite member" combo-box. If the calculation is saved and re-opened, the "opposite member" combo-box does not display the member that was originally selected (all of the other values are displayed). If changes are made and applied, the value shown in the combo-box (the first member in the list) is used in the calculation.

[ top ]

Known Issues

The following issues will be resolved in a future ShowCase Analyzer 7.01 patch.

• Specific iSeries V5R3 PTFs are required for relational reports that use the ShowCase JDBC driver

  Relational reports (including SQL Spreadsheet) that use the ShowCase JDBC driver require IBM iSeries V5R3 database and JDBC PTFs SI17835 and SI17838.

• Spaces in SQL Server table names

  SQL Server table names that include spaces fail in the SQL Query Builder wizard. For example, if you select a table named Order Details from which to build a query, a SELECT string is not returned in the SQL Query text section. The text section remains blank.

• Importing externally authenticated users

  An error occurs when importing externally authenticated users via the File | Import (.aru file) option in the Analyzer Administration Tools Client if the user's password is less than 6 characters.

• Hybrid analysis

  The Select Subset option does not display the correct members based on the defined Generation settings. Non-hybrid analysis databases display the correct members.

• ShowCase Essbase password prompt

  When the user profile in ShowCase Essbase is set to require a password change on next sign on, a password change prompt is not displayed when Analyzer attempts to access an Essbase database.

• Installation documentation correction

  The Analyzer Installation Quick Start document that shipped with the product lists incorrect server requirements for IBM® OS/400® V5R1, V5R2, and V5R3. The correct server requirements are:

  • V5R3: Java Group PTF SF99269 level 4 or later. Database and JDBC PTFs SI17835 and SI17838.

  • V5R2: Java Group PTF SF99169 level 20 or later.

  • V5R1: Java Group PTF SF99069 level 22 or later.

• DBCS Support

  Analyzer 7.01 is supported on a system that uses a double-byte character set (DBCS) to represent character data. To use the functionality, you must install the DBCS-supported CD. To order the CD, contact your sales representative.

  Prerequisites:

  • iSeries: V5R2 or V5R3 with latest CUM package and group PTFs.

  • PC: The PC used for Analyzer Server installation must use Windows 2000 Professional or XP Professional SP1.

  • See the full list of environment requirements in the Showcase Analyzer 7.01 Guide.

  When installing Analyzer on a DBCS system, DBCS users must connect to the iSeries with a 5035 CCSID profile rather than 5026. The 5035 CCSID is necessary for Java 1.4. If you do not use 5035, you may see a "failed to deploy" message during installation and the application will not run.

  To make sure Analyzer interprets Essbase data correctly, you must specify the Analyzer code page for your language set that matches the Essbase ASCII CCSID. See the “Specifying the Analyzer Code Page” section in the Showcase Analyzer 7.01 Guide for more details.

  Note: DBCS migration from STRATEGY 4.5 to Analyzer 7.01 is not supported.

• Excessive temp storage usage
  
  When managing large amounts of data, Analyzer continually increases temporary storage. IBM® iSeries PTF SI18225 is required to fix this issue on iSeries V5R3. Currently, no fix is available for V5R1 or V5R2.

  [ top ]