Sysview for DB2 filtering option changed in R18

[Anon Anon]

Prior to R18 when you entered a partial filter on a list screen it automatically added an asterisk "*" at the end.  In R18 this no longer occurs.  I have received comments from customers that they liked this feature and wonder why it no longer works?  Would like to here other peoples feelings on this change.

 

 

Prior to R18 when you entered a partial filter:

 

 

Insight would automatically add “*”

 

 

Now in R18:

 

 

No longer adds the “*”:

 

 

 

 

[Michael.K.Davis]

Unless CA had a good reason for removing it then I would say that it should be put back in.  Having SYSVIEW automatically wildcard the field for you was convenient.

[Denis Tronin]

Thank you for the feedback! We might change it back soon, but we wonder if there is anybody who would prefer to leave this filtering strict (no wildcard at the end)?

[Denis Tronin]

So does anybody believe that the SYSVIEW for DB2 should use the strict filtering for string values (no wildcard at the end)? We are up to change it back to r17 style...

[jeff.s.haekenkamp]

I like the automatic wildcard, so I vote that it should be put back in.

On a related subject, something that has always driven me crazy in Insight is that if nothing meets the filter criteria you enter, it wipes them all out and you have to start over.  Why can't it leave the filter criteria there and just tell you nothing meets the criteria?  (We're still on R17, so I don't know if this has been fixed in R18.)

[Michael.K.Davis]

I agree that this "bug" with SYSVIEW dropping the filter when nothing matches it should be fixed in R19.

[Denis Tronin]

Yes, it is fixed in both r18 and r19. Actually, the filtering is moved to UI task and is now available for any tabular report.

[Denis Tronin]

We have just released the PTF RO86041 for R19 that fixes the default string filtering. For R18 the fix will be available soon. Thank you for the feedback provided on this problem!

[Denis Tronin]

The PTF for R18 is RO86075.