I tend not to use ALL much and build my own cascades instead, and I hadn't run into this message before:
> PIPRIC064E Hexadecimal data missing after /. > PIPMSG003I ... Issued from stage 1 of pipeline 1. > PIPMSG001I ... Running "all (/word/ & //)". > PIPRIC192I ... Scan at position 12; previous data "(/word/ & //". "Hexadecimal" was puzzling here and sent me to the syntax diagram looking for special cases involving hex strings. I finally realized it really just meant "Data missing"--the string would be converted to hex in the generated subroutine pipeline, so the null string would have caused this message if that were run: *.input.0: !locate XA6969984 !locate X !*.output.0: The doc for ALL doesn't mention that null strings aren't allowed. Sure would be nice if they were just used as-is instead of failing. Even nicer if they were skipped--my own execs are full of code like this: If word = '' then locate = '' Else locate = '| locate x' || c2x(word) Nicest of all if they caused alternatives to be skipped as well, so that: all /word/ & // & (/more/ ! //) worked out to just: *.input.0: !locate XA6969984 !*.output.0: ¬R
