The change is dated December 17,1997. Why I don't know; particularly
why I did not allow both.
You should be all right if you test for
PIPELINE MODULE Modification 1.0110 sublevel 0022 (34 in decimal)
On 7 March 2011 22:43, Glenn Knickerbocker <[email protected]> wrote:
> I just stumbled on a message I abandoned long ago when it started to get
> into the confusion of VERIFY MATCH vs. VERIFY NOT. Way back when, John
> added a MATCH keyword, but then changed it to NOT--and in between,
> sadly, is when the product pipeline was frozen, so the product has MATCH
> and the uplevel version has NOT. Neither keyword has made it into
> either version of the document, probably because of just this confusion.
>
> Does anybody have a convenient workaround for occasional use? The
> simplest I've thought of is just to try one and use the other if it fails:
>
> 'PIPE literal verify match "x" | runpipe'
> If rc = 0 then match = 'match'
> Else match = 'not'
>
> 'PIPE ... | verify' match ...
>
> If I used it more often, it would be worth putting this into a front-end
> REXX stage, but for the rare use here and there it seems more
> straightforward to keep it in my main code.
>
> ¬R
>
