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
