|
Isn't this behaviour exactly the same as the F17 filters in good old PDM?
Met vriendelijke groeten / Best regards,
Peter Colpaert
Software Engineer - PLM Development Team Lead R&D IT
Philips Consumer Luminaires
Industrieterrein Satenrozen 11, 2550 Kontich, Belgium
Tel: (+32) 3/459 13 17
Email: Peter.Colpaert@xxxxxxxxxxx
Home Office on Wednesdays and Fridays
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Calabro
Sent: vrijdag 1 juli 2016 19:55
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Member filter issue...
On 7/1/2016 12:55 PM, CRPence wrote:
On 01-Jul-2016 10:08 -0500, Brian Johnson wrote:Perfectly sensible advice. Here's what F1 tells me:
Mouse or not... fabulous prize will be awarded (not!) for a filterSearch the help text or docs for, if there exists support for, an
that selects members with member text that contains an asterisk.
/escape/ character in that context.
'Use this dialog to change your filter. Filters can contain one or more filter strings. In the Remote Systems view, when a filter is expanded, the results of resolving all the strings are concatenated together. Use this dialog to add additional strings, and to order, delete or change the strings. Use the context menu on a string for additional actions.'
Some nomenclature explanation might help.
On the left are a list of named 'things' called 'Filter strings'. Each of these named objects contains an assortment of search / filter criteria. In order, these are:
Library
File
Member filter
Member text
The behaviour for the top two (Library and File) are close to what IBM i programmers expect of IBM i commands accepting generic names. Filtering on Library QGPL, File Q* would return all the files beginning with Q in library QGPL.
The member filter behaves a bit differently. It takes a pattern somewhat reminiscent of OPNQRYF. Let's say that my chosen source file has members named EXAMPLE1 through EXAMPLE38 as well as one member named EXPAT_H, one named HTTPXMLR4, and one named XMLSTUBR4. I could filter for all the members beginning with EX by putting EX* in the Member filter. I could filter for all the members containing an X somewhere in their name by using *X*. I could find all the members ending with a 3 by using *3.
The Member text behaves different to the prior two. It does an implicit wildcard search. So putting in EX gives me all the EXAMPLE members as well as the EXPAT_H member. There are two special values allowed: * (for don't restrict the search) and *BLANK, which returns a list of members not having text specified.
The documentation is... a work in progress. The support portal has links to Rational Developer for i documentation, but of course the resolved page is the AIX / Linux version. I'm sure Developerworks have a working link but finding the right place in DW takes more cognitive energy than I have to spare at the moment. Oh, and the help within the product throws an HTTP 500 error. A reboot of my PC will probably cure that but I can't really send my time down that rabbit hole. It's a little crazy when it takes longer to restart my PC than to restart the IBM i operating system, but it looks I've reached the pinnacle of my career.
So once again, everything I think I know comes from empirical evidence; actually trying it out.
--
--buck
Visit wiki.midrange.com and register for an account. Edit a page that helps you, and because it's public, you'll help someone else, too!
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
