"John P. Hartmann" wrote: > The commit mechanism has a lot more to it than Glenn lets on.
Right, my point was to simplify it to a starting point for Bob. In writing a REXX stage, all he has to worry about is getting from -1 to 0. > For < no file|, the nonextant file is caught in the syntax check Whooops! I even saw in your paper that < starts at level 0. To use your example from there of LOCATE checking its streams, then: pipe l: locate | l: | > exist file a As you wrote there, > locate is dispatched at commit level -2 as before; when it now finds that its > secondary > input stream is connected, it issues a message and terminates with a non-zero > return code. *Then*, when > sees that nonzero return code, it knows not to erase EXIST FILE. > The example for PIPE AHELP COMMIT shows how a REXX program can check > the return code from other programs as to whether it should continue, That's the example that doesn't make any sense to me. The COMMIT command doesn't make any difference in the example as written. It would be done implicitly anyway as soon as the stage issued OUTPUT, and the result would be exactly the same. ¬R
