IBM Support

PI23304: INCONSISTENCY IN FILTER DXL WHEN FILTER SAVED IN VIEW IS NO LONGER VALID

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If a filter saved as part of a view is loaded (i.e. as part of
    loading that view) the filter will correctly be reported as
    invalid, but certain filter related DXL will behave
    inconsistently.
    
    To recreate:
    
     - create a module with an enumeration attribute
     - apply a filter such as "(enumAttr == value1) AND (NOT
    (Attribute 'Object Text' contains 'anyString'))" where "value1"
    is a valid enumeration value
     - save the filter as part of a view
     - switch to the Standard View then remove "value1" from the
    enumeration type
     - now, when reloading the saved view, you will see a message
    detailing that the saved filter is no longer valid.
    
    That is good, but subsequently trying to establish what the
    filter is by using DXL is problematic
    
     - run code such as the following:
    
    "
    Filter f = current
    Module m = current
    string s = stringOf(m, f)
    
    print s "\n"
    print getCompoundFilterType_ f
    print filterTypeAnd
    "
    
    The output suggests that stringOf() returns the active filter
    (i.e. without the enumeration condition) but that
    getCompoundFilterType_() is using the version of the filter
    saved in the view.
    
    This can cause problems when trying to establish the actual
    filter e.g.  if getCompoundFilterType_() returns filterTypeAnd,
    you would assume that each compound part could be retrieved by
    using getComponentFilter_(), however, when supplied with an
    index of greater than 0 a run-time error is produced.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of certain filter DXL functions.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If a filter saved as part of a view is loaded (i.e. as part  *
    * of loading that view) the filter will correctly be reported  *
    * as invalid, but certain filter related DXL will behave       *
    * inconsistently.                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This has been resolved in the 9613 release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI23304

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-08-05

  • Closed date

    2015-10-23

  • Last modified date

    2015-10-23

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

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

Fix information

  • Fixed component name

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R961 PSY

       UP



Document information

More support for: Rational DOORS

Software version: 9.3

Reference #: PI23304

Modified date: 23 October 2015