Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes

[<hp...@we...>]

((This reply I send intentionally "to all".))

Am 03.06.2022 um 14:54 schrieb René Jansen:
>>>> Well, I hope NetRexx Pipelines allows home-made stages like this.
>>>
>>> Yes, certainly. The source of all the stages is in NetRexx. Did you check out the source from Github or SourceForge (I keep it in two places because it limits the exposure from outages).
>>
> The NetRexx repo on GitHub is https://github.com/RexxLA/NetRexx <https://github.com/RexxLA/NetRexx> , stages are at https://github.com/RexxLA/NetRexx/tree/master/src/org/netrexx/njpipes/stages <https://github.com/RexxLA/NetRexx/tree/master/src/org/netrexx/njpipes/stages>

Thank you. Lessons learned? Hints are nice, links are better ;)

> But I see you found the SourceForge repo.

Yes, after some time.

>>> [...]
>> So this is the only option users may add their DIY stages?
>
> Not at all: these are the included stages (‘programs’ I think the book calls them now) and show how things are done at the moment, but you can start a homegrown stage at literally any place on your file system.

Ok, where is this documented so I may read along and ask less
tiring questions.

> I think this is about the minimal boilerplate:

Hmm... you think... and "me think", I found a tutorial in chapter
5 of NetRexx Pipelines Guide and Reference, alas no reference
documentation yet.

> import org.netrexx.njpipes.pipes.
>
> class bagvendt extends stage
>
> method run()
>
>     loop forever
>        line = Rexx peekto()
>        output(line.reverse())
>        readto()
>     catch StageError
>        rc = rc()
>     end -- loop forever
>     exit(rc*(rc<>12))

Are there templates somewhere like those from by Steve Hayes here
http://vm.marist.edu/%7Epipeline/#Skeleton

Now, how does our project go on? You "delivered" already something
for the first pipeline

> call RxPipe '< "' || fn || '"!nlocate 1 /*/!varset'

but I was not yet able to grasp your solution in detail. So my
questions are:

i) How to start a NetRexx Pipelines from ooRexx?

ii) how is the content of 'fn' transferred from "here" to "there"?

iii) how must a varset or varload stage look like with (almost)
all options as the role model?

Questions about the details: iii-a) would it make sense in NetRexx
Pipelines to distinguish PRODUCER vs MAIN? In other words, I even
do not know yet if NetRexx Pipelines offer something like callpipe
and addpipe.

iii-b) The optional number (integer, positive, including 0) to
define which ancestors' variable pool to use -- is that also
doable and useful within NetRexx Pipelines? ooRexx included? (On
z/VM I may run an Exec A which starts a FORTRAN which calls an
Exec B which has access (read and write) to variables of Exec A,
just using the correct number in varset or similar stages.)

iii-c) The keywords SYMBOLIC and DIRECT are IMHO not mandatory,
since the later might be source of some trouble.

iii-d) option COMMENTS makes a preceding filter obsolete, what I
would appreciate.

iv) how may a varload or varset stage set variables of ooRexx?
What is question iii-b) again, but mandatory now.

I hope none of these questions will dig out a show-stopper.

Have a nice WE
M.