PM42182: Search value problem when using Analytic Report to search for objects in SA

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as Permanent restriction.

Error description

  • Search value problem when using Analytic Report to search for
    objects in SA. When we create a report or analytic report with a
    'starts with' condition, then for some names (names with
    spaces), it works only if we have a beginning quote in the value
    part of the condition.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When we create a report or analytic report with a 'starts
    with' condition, then for some names (names with spaces), it
    works only if we have a beginning quote in the value part of
    the condition.
    

Problem conclusion

  • System Architect  is working as designed here and the belief is
    that this should not be changed. In this case the user is perfor
    ming a comparison on a listof field and here any item containing
     a space is saved bounded in quotes, as can be seen both in the
    Advanced Editor and the Property pane (by selecting the property
     and observing the content of the bottommost pane).
    Changing this behavior may upset users.
    Otherwise since only the first stored entry will be compared, th
    e comparison is of reduced usefulness anyway.
    
    The question is:
    
    why the items in a listof field containing a space are saved bou
    nded in quotes?
    
    The answer:
    
    Space is used as a separator in expressions and minispecs. The p
    arser needs the quotes in order to distinguish between definitio
    n names, operators, verbs, etc.
    
    Changing this behavior is not simple, and it is risky. SA has ha
    d numerous problems over the years cause by quotes vs. no quotes
    . This parser will not be touched. This will not be 'just a smal
    l change'. There is code everywhere, that deals with quotes and
    knows what to do.
    
    Change is good, but risky because changes to parser can have rip
    ple effects
    
    We're not trying to avoid it. It's a tough decision. We're comin
    g down on the side of risk, therefore the decision is not to cha
    nge this.
    
    Please see the related technote:
    
    http://www-01.ibm.com/support/docview.wss?uid=swg21617438
    

Temporary fix

Comments

  • Working as designed.
    Space is used as a separator in expressions and minispecs. The p
    arser needs the quotes in order to distinguish between definitio
    n names, operators, verbs, etc.
    To change this is too high a risk.
    
    Please see the related technote:
    
    http://www-01.ibm.com/support/docview.wss?uid=swg21617438
    

APAR Information

  • APAR number

    PM42182

  • Reported component name

    TLOGIC SYS ARCH

  • Reported component ID

    5724V68SA

  • Reported release

    B30

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-21

  • Closed date

    2012-11-13

  • Last modified date

    2012-11-19

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational System Architect

Software version:

11.3

Reference #:

PM42182

Modified date:

2012-11-19

Translate my page

Machine Translation

Content navigation