Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Rob van der Heij
Indeed, WILDCARD is aimed at what LISTFILE does, so you'd bend a few pipes to make that happen. Hoping I don't confuse you even more: /* */ 'PIPE (END \ name T1.EXEC:2)', '\ literal johnboy jimboy somegirl jimboys ', '| split ', '| spec w1 1 ,x x, nw', '| w: if wildcard ,j*boy x x, ',

Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Stanislawski, Shawn (National VM Capability)
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,

Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Stanislawski, Shawn (National VM Capability)
Just to double check my understanding regarding the capabilities of the WILDCARD stage: pipe cms listfile * * a (noh | wildcard 1.30 /*PROFILE*/ | console This does not give any output because "listfile * * a (noh" contains 3 words, and WILDCARD's delimited string here does not specify 3

Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Rob van der Heij
On Wed, 31 Oct 2018 at 16:25, Stanislawski, Shawn (National VM Capability) < shaw...@dxc.com> 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 | ...

Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Stanislawski, Shawn (National VM Capability)
Ah, apologies, you're right, failed to provide that piece: original record is desired at the end. --Shawn S. -Original Message- From: CMSTSO Pipelines Discussion List [mailto:CMS-PIPELINES@VM.MARIST.EDU] On Behalf Of John P. Hartmann Sent: Wednesday, October 31, 2018 10:07 To:

Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread John P. Hartmann
Use CHOP 30|COPY|SPLIT|WILDCARD and JUXTAPOSE to prefix the remainder of the record by each word. It should be pretty easy to adapt WILDCARD to serach for the keyword, as you suggest. You'll have to do a bit of contortion to get the topology just right. I'm sure Rob can elaborate and also get

Re: [CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Rob van der Heij
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

[CMS-PIPELINES] Wildcard searching

2018-10-31 Thread Stanislawski, Shawn (National VM Capability)
Want to filter a stream of records, letting only certain ones through based on a keyword in each record. What we know: -the keyword could be anywhere in the first 30 characters -the keyword is space delineated (no leading space if keyword is first word) -the first and last part of that keyword