Regarding: "But if you're looking for multiple keywords, FIND may get tedious since you'd need a cascade to check them. I have been known to load a LOOKUP table with all the possible forms of the keyword, but that's only realistic when you're dealing with abbreviations."
You're quite right, would want to look for a list of multiple keywords, where each record can have only 1 match (though same match might happen in different records). But LOOKUP doesn't support wildcard matching, right? (Center of the keywords aren't known, only the number of unknown characters in each keyword.) --Shawn S. -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Rob van der Heij Sent: Wednesday, October 31, 2018 10:37 To: [email protected] Subject: Re: [CMS-PIPELINES] Wildcard searching On Wed, 31 Oct 2018 at 16:25, Stanislawski, Shawn (National VM Capability) < [email protected]> wrote: > Ah, apologies, you're right, failed to provide that piece: > original record is desired at the end. > So you could do something like this: ... input records | o: fanout | j: juxtapose | ... result \ o: | chop 30 | split | ... select your keys | chop 0 | j: The problem I envisioned is that you might have multiple keys match, in which case JUXTAPOSE would produce multiple copies of your input record. You could do UNIQUE FIRST but that's a bit naughty ;-) That's why I encouraged you to explore PREDSELECT which sends a single copy of each input record to either primary or secondary output, depending on whether it got a trigger (from your keyword selection). Sir Rob the Plumber -----Original Message----- From: CMSTSO Pipelines Discussion List [mailto:[email protected]] On Behalf Of Rob van der Heij Sent: Wednesday, October 31, 2018 09:33 To: [email protected] Subject: Re: [CMS-PIPELINES] Wildcard searching Shawn, The approach I would take is to take that part of the records where you want to search, and split those parts into words. That puts the words at the start of the record. I suppose you could get multiple hits from the original record, so PREDSELECT would be your friend to do the vetting of the input records. But if you're looking for multiple keywords, FIND may get tedious since you'd need a cascade to check them. I have been known to load a LOOKUP table with all the possible forms of the keyword, but that's only realistic when you're dealing with abbreviations. Sir Rob the Plumber DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. --.
