IBM Support

JR33286: LIMITING DOMAIN WITH MIN/MAX VALUES DOES NOT REFRESH IN THE DOMAIN AND COMPLETENESS TAB

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • This customer is seeing a problem with the IA client- it appears
    the client doesn't do anything when he clicks the RELOAD button
    and specifies a min and max value in the Domain and Completeness
    tab.  He expects the Frequency Distribution list to change to
    include only the values that fit in the min/max values, but
    nothing happens.
    

Local fix

  • A workaround for the issue is to
    Enter min / max and pressing 'Enter' key while in their fields
    and then selecting Reload.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Usage of the Domain & Completeness Screen in IA UI,
    specifically when the Domain type has been specified as Range.
    ****************************************************************
    PROBLEM DESCRIPTION:
    1. The Minimum and Maximum value must be an existing value in
    the table as opposed to any value
         2. After accepting the
    Minimum and Maximum value, the "Invalid  values" table is not
    repainted to list the Invalid values.    Ironically, if the
    user saves the settings, switches to       another column,
    and then comes back to this column, the  "Invalid"
    values table is populated.
             3. After entering a value for
    Minimum, if Save was clicked,     user got an error message
    "Error writing to Scratch space, Invalid number". It
    seemed that the error only occurred if     either the Minimum
    or Maximum box did not have a value. If both boxes had values
    that existed in the table, the Save seemed to work. Users are
    also allowed to specify the Minimum and Maximum in the FD box
    instead of the Minimum/Maximum boxes, and this is the user's
    preferred mode of operation. So, the Save should not fail as
    long as the Minimum and Maximum values have been
    specified. If one or both values are not specified, it should
    pop up an error message not an application failure.
    ****************************************************************
    RECOMMENDATION:
    Upgrade to Information Analyzer 8.1 Rollup Patch 4. This change
    is also included in 8.1 Fix Pack 1.
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR33286

  • Reported component name

    WIS INFORM ANAL

  • Reported component ID

    5724Q36IA

  • Reported release

    810

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-09

  • Closed date

    2009-08-05

  • Last modified date

    2009-12-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R810 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSZJLG","label":"InfoSphere Information Analyzer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
18 December 2009