Hi John, that depends entirely on your definition of “reasonable.” Ours might be different.
Mine is: you are able to work “in the vein of” CMS Pipelines by being able to compose a commandline consisting of recognisable VM pipeline stages, on any computer that runs a JVM. A big difference at the moment is that a pipeline in the current implementation is compiled into a (java) .class - the NJPipes implementation predated the NetRexx interpreter. (Because in contrast to Classic Rexx, NetRexx first had a compiler and after 2000 an interpreter.) Also, because of the nature of Unix command lines, it is easier to use ! as a stage separator. The impedance mismatch between Java and CMS or TSO is certainly there, we can look how fork() would be handled for example, but if NetRexx was still supported on CMS by IBM I could show you commandlines that are identical. NetRexx is a dialect of Rexx, and as such most programs will look different. This also goes for non-pipeline filter programs. Readto() and Peekto() are there, as is output(). This makes it not too difficult to use ‘more or less’ the same Rexx code, and the optimist in me would still call that ‘reasonably’ portable. I made my first stages when I only could write Rexx and no NetRexx, so it is not too far off. You have interested me now in the pipelines regression test; if that runs on text data and has no EBCDIC dependencies I am inclined to use that, if I had it, to certify the individual stages. I knmow people like Jeff Hennick and Ed Tomlinson went to great lengths to be compatible with at least the level of Pipelines that they had access to. Is this regression test open sourced? Or available somewhere with favorable license conditions for the Rexx Language Association? best regards, René Jansen. > On 22 Mar 2019, at 12:54, John P. Hartmann <[email protected]> wrote: > > How can you say that when it has not passed the pipelines regression test? > > Can you move at least pipelines REXX filters between VM and your workstation > without change? > > On 3/22/19 17:49, René Jansen wrote: >> The implementation (by Ed Tomlinson) follows VM and is reasonably complete.
