netrexx-pipelines

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

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

It's WE of Pentecost, time for something more relevant than
variations of Pipelines. But I'll try to reply most of my
questions by myself, might result in some more insight about all
the obstacles of this drudgery.

Am 03.06.2022 um 18:13 schrieb ((ich)):
> [...]
> 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?

In C:\prgm\NetRexx\bin I had renamed the PIPE.BAT to HIPE.BAT what
should allow coexistence of OS/2 Pipelines with NetRexx Pipelines.
Works from the command line of a cmd window.
(I renamed it again to RIPE.BAT, just as objective to bring it to
a maturity worth to publish.)

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

What's possible from the command line will also work from Rexx,
ooRexx, and so on. But the arguments to RIPE (PIPE.BAT renamed)
must be clasped/surrounded by double quotes. A simplistic test:

> /* ooRexx */
> fn = vilma.ini
> ripe '"<' fn '|term"'

Works. (Quite funny, when I tried this first it failed, allegedly
function 'term' not found.)
When I look into RIPE.BAT there is no procedure, just one single
line to involve Java (to my comprehension). So it should be
possible to set variable ripe to avoid the need of that renamed
batch file.

> /* ooRexx */
> nrh = value("NETREXX_HOME", , "ENVIRONMENT")
> ripe = '@java -cp "'nrh'\lib\NetRexxF.jar;%CLASSPATH%"',
>  'org.netrexx.njpipes.pipes.runner'
> fn = vilma.ini
> ripe '"<' fn '|term"'
Works. So the BAT file is obsolete for this project.

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

First I wanted to see if the ooRexx function 'value' works the
same under NetRexx. It will -- hopefully -- be documented in
"NetRexx Language Reference", ISBN 978-90-819090-1-3, which shows
on the title page Mike Cowlishaw and REXXLA as author (I doubt. In
addition, Adobe Acrobat Reader shows as first bookmark 'List of
Tables' which is linked to 'Content' on page upper-case II, there
'List of Tables' is indicated to be on page upper-case VII, a
mouse-klick on this entry does just nothing, while the 'List of
Tables' is in fact on page upper-case VIII. Sure, this could be a
negligible detail, if not details stand for the whole. The
responsible publisher of this edition is mentioned on page
upper-case I, but who involved them? Mike Cowlishaw?)

Back to the subject. I expected a language reference documentation
to be structured according the language, something like: A-general
concept, B-keyword instructions, C-functions, etc. Since I still
have REXX in mind as I know it since VM/SP my assumption was a
fail. Similar to the "clash of the cultures" I encountered with
ooRexx I see it now with NetRexx. Instead of

> say length("ABC")

I have to put it this way:

> say "ABC".length

What a progress! Re-use of old-style REXX routines impossible.

OK, back to the subject.
Additional question: if I would program a VARLOAD stage or alike,
and set there some variables according the data trickling through
the pipe, would those be set within the VARLOAD routine only or
for the NetRexx program which called the pipe in question? Would
this also be possible from ooRexx? Probably not, but is there a
chance to access a "common pool" from both "dialects"? Something
adequate the GLOBALV concept of VM/CMS? Well, that would require
some kind of "pull" in ooRexx after the NetRexx pipe finished, a
"push" of the results (variables set directly) would be more
appropriate.

Sorry, with my nonexisting knowledge of NetRexx I'm stuck. At
least I was able to answer two questions on my own. Now it's the
turn for real experts.

Best,
M.

Re: [netrexx-pipelines] NetRexx llist works different than expected

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

There is one obvious change since I subscribed, my mail system now
shows a "Reply to List" button for mails from this list. I use it
this time as a test, next reply I'll send to all. So we will find
out if mails are self-acting distributed from the list or not.
/M.

Am 03.06.2022 um 12:34 schrieb hp...@we...:
> Hello René!
>
> I found no "delivery options" in my SourceForge profile but saw
> not to be member in any mailing list. So I subscribed to the
> netrexx-pipelines mailing list. Let's see how this pans out.
> /M.
>
> Am 03.06.2022 um 11:38 schrieb René Jansen:
>> What probably would help is to set ‘delivery options’ with your
>> userid on this mailing list in SourceForge, netrexx project.
>
>
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

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.

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

[René J. <rvj...@xs...>]

Hi Mike,

> On 3 Jun 2022, at 14:31, hp...@we... wrote:
> 
>>> 
>>> 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).
> 
> Found https://github.com/rvjansen/netrexx-site <https://github.com/rvjansen/netrexx-site> but no source of
> stages in there.
> 
No, that is the website; this is a useful repository for finding old NetRexx versions online.

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>

But I see you found the SourceForge repo.

>> We keep all the stages in src/org/netrexx/njpipes/stages. Most are put together by Jeff Hennick so I hope he’ll join this conversation sometime.
> 
> Clicking on 'Files' in SourceForge shows:
> "This project has no files."
> Then ... at last, found it. Nice :)
> 
> So this is the only option users may add their DIY stages?
> 
> /M.

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.

I think this is about the minimal boilerplate:

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))
   
Best regards,

René.

Re: [netrexx-pipelines] NetRexx llist works different than expected

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

Hello René!

I found no "delivery options" in my SourceForge profile but saw
not to be member in any mailing list. So I subscribed to the
netrexx-pipelines mailing list. Let's see how this pans out.
/M.

Am 03.06.2022 um 11:38 schrieb René Jansen:
> What probably would help is to set ‘delivery options’ with your userid on this mailing list in SourceForge, netrexx project.

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

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

>> On 3 Jun 2022, at 04:53, hp...@we... wrote:
>> ((Reply to a mail I missed))
>>>> [...]
>
> The Pipelines Guide shows some examples of how nrws is an apt environment for pipeline experimentation. The main nrws documentation is in the Programming Guide. [...]

I found no way to change the colour of the 'nrws>' prompt to the
left and the additional info on the RHS. It's dark blue on black
and for me just not existent. Even if I change the background of
the cmd window this two fields insist on their own background
colour: black.

>>> nrws> say hello                                                        initial 1
>>> 2 +++ say hello;
>>>   +++     ^^^^^
>>>   +++ Error: Result of this expression cannot be just a type; it must have a va
>>> lue
>
> In NetRexx, there is no literal value of an undeclared string. If you look at the first VM manuals, those were all over them, and they disappeared from the examples and a ’signal on novalue’ was introduced. Following that trend they were removed from NetRexx.

Fair enough -- seems a tendency I missed. Sorry.

>> BTW, the nrws description uses every now and then the term "home
>> directory", once even "top level home directory". May I assume
>> this is the same as I set at some point during installation
>> procedure in the NETREXX_HOME system variable (and the top level
>> home directory to be the same)?
> No, this is your home directory, I think in windows referred to as %HOME%.

Stackoverflow unveils: "Home" on Windows is %userprofile%
Was asked more than 10 years ago. Tested with nrws -- works.

>> ...and so on. Did you read along "the Book" about varset at
>> http://vm.marist.edu/~pipeline/pipeline.pdf ?
>> I know it's dated, but -- hobbyist I am -- I'm removed from
>> Pipelines evolution ever since the Runtime Library Distribution
>> was updated for the last time.
>>
> Not yet, but I will today. Seems like a handy addition.

Sure, there are other ways to read defaults from disk, for example
read an INI file and _interpret_ it line by line. Offers the
optional risk of "bad" REXX clauses in it. Setting variables only
is less jeopardy.

>>> So that does more or less what you want already - the source redirect <, the nlocate works. If you want we can make a varset stage, I think we don’t have that at the moment but it cannot be too hard.
>>
>> No, we should go all-in, if NetRexx Pipelines does not have a
>> varset stage yet it is a good test (for me to learn and for
>> NetRexx to point out) how to add those 'on the fly', analogous to
>> CMS Pipelines (filetype REXX). [...]

I have to weaken my request a bit by adding 'if possible and
purposive'. At least I also had to adopt my "CMS-pipe-thinking" to
the limited capabilities and many pitfalls of OS/2 Pipelines. So
my only goal of this change-over to NetRexx Pipelines is nothing
but running VilMA and -- if installation of NetRexx is as simple
as /younameit/ -- maybe publishing it.

>> 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).

Found https://github.com/rvjansen/netrexx-site but no source of
stages in there.

> We keep all the stages in src/org/netrexx/njpipes/stages. Most are put together by Jeff Hennick so I hope he’ll join this conversation sometime.

Clicking on 'Files' in SourceForge shows:
  "This project has no files."
Then ... at last, found it. Nice :)

So this is the only option users may add their DIY stages?

/M.

Re: [netrexx-pipelines] NetRexx llist works different than expected

[René J. <rvj...@xs...>]

What probably would help is to set ‘delivery options’ with your userid on this mailing list in SourceForge, netrexx project.

René.

> On 3 Jun 2022, at 11:02, René Jansen <rvj...@xs...> wrote:
> 
> It is not you, this is a pain. I must have a look if I can change that reply-behavior somewhere.
> I do a ‘reply all’ and then I delete the user email and shift the list address to to:.
> 
> René.
> 
>> On 2 Jun 2022, at 23:09, hp...@we... wrote:
>> 
>> Hi!
>> 
>> I am quite sure, it ain't my fault, it's NetRexx list what works
>> different than I'm used from CMS-PIPELINES list. Without a closer
>> look to the address fields I pressed all the time 'reply' or
>> 'reply all' and assumed it would show up on the NetRexx-pipelines
>> list. Alas no.
>> 
>> Now I have replied to a mail from Jason Martin inadvertently with
>> no copy to NetRexx-pipelines, same time I find on the internet
>> site "netrexx-pipelines Mailing List for NetRexx" an answer from
>> René which did not show up in my email since hours now. Almost
>> impossible to reply because the sourceforge list does not offer a
>> reply button. (I'll copy what's important to a reply by mail.)
>> 
>> Sorry if it's me causing useless trouble.
>> M.
>> 
>> 
>> _______________________________________________
>> netrexx-pipelines mailing list
>> net...@li...
>> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines
> 
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

Re: [netrexx-pipelines] NetRexx llist works different than expected

[René J. <rvj...@xs...>]

It is not you, this is a pain. I must have a look if I can change that reply-behavior somewhere.
I do a ‘reply all’ and then I delete the user email and shift the list address to to:.

René.

> On 2 Jun 2022, at 23:09, hp...@we... wrote:
> 
> Hi!
> 
> I am quite sure, it ain't my fault, it's NetRexx list what works
> different than I'm used from CMS-PIPELINES list. Without a closer
> look to the address fields I pressed all the time 'reply' or
> 'reply all' and assumed it would show up on the NetRexx-pipelines
> list. Alas no.
> 
> Now I have replied to a mail from Jason Martin inadvertently with
> no copy to NetRexx-pipelines, same time I find on the internet
> site "netrexx-pipelines Mailing List for NetRexx" an answer from
> René which did not show up in my email since hours now. Almost
> impossible to reply because the sourceforge list does not offer a
> reply button. (I'll copy what's important to a reply by mail.)
> 
> Sorry if it's me causing useless trouble.
> M.
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

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

[René J. <rvj...@xs...>]

> On 3 Jun 2022, at 04:53, hp...@we... wrote:
> 
> ((Reply to a mail I missed))
>>> So once more without the ZIP -- René, IMO you got it in your
>>> personal mail, holler if not.
>>> 
>> I have it.
> 
> Good. So you may take a closer look to the files VilMA uses or the
> description of a "session". Probably this gives a bit more insight
> than the bare REXX code only.
> 
> I skip all "documentation" related issues, I know it's not easy to
> find a description level that fits for a non-uniform target group.
> 
>> I would suggest to use ’nrws’ (the Netrexx Workspace) for experiments with pipes.
> 
> 'Netrexx Workspace' is neither mentioned in the NetRexx QuickStart
> Guide nor in NetRexx Language Reference, there is a chapter about
> it in NetRexx Programming Guide and one in NetRexx Pipelines Guide
> and Reference. In that case I assume the Pipelines Guide will show
> supplementary information only and all fundamentals about /nrws/
> are in the Programming Guide where I start.

The Pipelines Guide shows some examples of how nrws is an apt environment for pipeline experimentation. The main nrws documentation is in the Programming Guide. I will make sure to refer to it from the Quickstart Guide and the Reference, but nrws was a late addition - it existed for 20 years already, and I came across it while starting to write a simple repl for NetRexx. It can do some nifty stuff of which I am using about 5%. On Windows an extra added value is that it logs your session in the nrws.history file; we have that standard on *nix from the shell. With the default (without a nrws.properties file in the home directory (the user home directory) I do not see the timings that I want to see, and it will not preload the pipeline classes - but this has changed in NetRexx 4.04.)

> BTW, since decades on
> VM/CMS now with ooRexx, I use a very simplest "type REXX on the
> command line" tool, consisting of just three lines:
> 
>> /* interactive REXX */
>> trace '?R'
>> address ''
> 
> Until I know how to run this with NetRexx I'll use 'nrws' -- which
> shows something daunting at first try:
> 
>> nrws> say hello                                                        initial 1
>> 2 +++ say hello;
>>   +++     ^^^^^
>>   +++ Error: Result of this expression cannot be just a type; it must have a va
>> lue
> 

In NetRexx, there is no literal value of an undeclared string. If you look at the first VM manuals, those were all over them, and they disappeared from the examples and a ’signal on novalue’ was introduced. Following that trend they were removed from NetRexx.

> This contradicts REXX principles of primary importance, at least
> from my point of view. Fortunately we'll replace only the
> pipelines, not the REXX dialect.
> 
> BTW, the nrws description uses every now and then the term "home
> directory", once even "top level home directory". May I assume
> this is the same as I set at some point during installation
> procedure in the NETREXX_HOME system variable (and the top level
> home directory to be the same)?
No, this is your home directory, I think in windows referred to as %HOME%.

> 
> Now I slooowly start to grasp, what you sent recently had been
> screen shots of a nrws session:
> 
>> ➜  test git:(master) ✗ cat varset.nrx
>> vars =''
>> address pipe with output stem vars
>> "< vars.ini | nlocate 1 /*/ | cons"
>> do i=1 to vars[0]
>>  say vars[i]
>> end
> 

No, these were just cats from a macOS terminal. To show source as the content of a file.

> ...and so on. Did you read along "the Book" about varset at
> http://vm.marist.edu/~pipeline/pipeline.pdf ?
> I know it's dated, but -- hobbyist I am -- I'm removed from
> Pipelines evolution ever since the Runtime Library Distribution
> was updated for the last time.
> 
Not yet, but I will today. Seems like a handy addition.

> The comment for the pipe in line 94 of VilMA.rx is a silent hint,
> that the nlocate stage is only necessary because OS/2 Pipelines
> does not offer the COMMENTS option of varset.
> 
>> So that does more or less what you want already - the source redirect <, the nlocate works. If you want we can make a varset stage, I think we don’t have that at the moment but it cannot be too hard.
> 
> No, we should go all-in, if NetRexx Pipelines does not have a
> varset stage yet it is a good test (for me to learn and for
> NetRexx to point out) how to add those 'on the fly', analogous to
> CMS Pipelines (filetype REXX). varset is almost something like
> 
> signal on error
> do forever
>   'READTO record'		/* don't mind delay */
>   parse var record sc +1 vn (sc) sv
>   if pos(sc, "* ") > 0,	/* see the COMMENT option */
>    then iterate
>   upper vn			/* optional, see also varload */
>   dummy = value(vn, sv, ...)	/* for variable pool of caller */
> end
> error:; exit rc * (rc <> 12)	/* or whatever rc is OK */
> 
> Well, I hope NetRexx Pipelines allows home-made stages like this.
> Maybe this "take in INI file" pipe could then look something like:
> 

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).
We keep all the stages in src/org/netrexx/njpipes/stages. Most are put together by Jeff Hennick so I hope he’ll join this conversation sometime.


> NetRexx Pipe "<" fn "|varload symbolic"
> 
> (see the differences in the defaults of varset and varload.)
> 
> Best,
> M.
best regards,

René.

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

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

((Reply to a mail I missed))
>> So once more without the ZIP -- René, IMO you got it in your
>> personal mail, holler if not.
>>
> I have it.

Good. So you may take a closer look to the files VilMA uses or the
description of a "session". Probably this gives a bit more insight
than the bare REXX code only.

I skip all "documentation" related issues, I know it's not easy to
find a description level that fits for a non-uniform target group.

> I would suggest to use ’nrws’ (the Netrexx Workspace) for experiments with pipes.

'Netrexx Workspace' is neither mentioned in the NetRexx QuickStart
Guide nor in NetRexx Language Reference, there is a chapter about
it in NetRexx Programming Guide and one in NetRexx Pipelines Guide
and Reference. In that case I assume the Pipelines Guide will show
supplementary information only and all fundamentals about /nrws/
are in the Programming Guide where I start. BTW, since decades on
VM/CMS now with ooRexx, I use a very simplest "type REXX on the
command line" tool, consisting of just three lines:

> /* interactive REXX */
> trace '?R'
> address ''

Until I know how to run this with NetRexx I'll use 'nrws' -- which
shows something daunting at first try:

> nrws> say hello                                                        initial 1
>  2 +++ say hello;
>    +++     ^^^^^
>    +++ Error: Result of this expression cannot be just a type; it must have a va
> lue

This contradicts REXX principles of primary importance, at least
from my point of view. Fortunately we'll replace only the
pipelines, not the REXX dialect.

BTW, the nrws description uses every now and then the term "home
directory", once even "top level home directory". May I assume
this is the same as I set at some point during installation
procedure in the NETREXX_HOME system variable (and the top level
home directory to be the same)?

Now I slooowly start to grasp, what you sent recently had been
screen shots of a nrws session:

> ➜  test git:(master) ✗ cat varset.nrx
> vars =''
> address pipe with output stem vars
> "< vars.ini | nlocate 1 /*/ | cons"
> do i=1 to vars[0]
>   say vars[i]
> end

...and so on. Did you read along "the Book" about varset at
http://vm.marist.edu/~pipeline/pipeline.pdf ?
I know it's dated, but -- hobbyist I am -- I'm removed from
Pipelines evolution ever since the Runtime Library Distribution
was updated for the last time.

The comment for the pipe in line 94 of VilMA.rx is a silent hint,
that the nlocate stage is only necessary because OS/2 Pipelines
does not offer the COMMENTS option of varset.

> So that does more or less what you want already - the source redirect <, the nlocate works. If you want we can make a varset stage, I think we don’t have that at the moment but it cannot be too hard.

No, we should go all-in, if NetRexx Pipelines does not have a
varset stage yet it is a good test (for me to learn and for
NetRexx to point out) how to add those 'on the fly', analogous to
CMS Pipelines (filetype REXX). varset is almost something like

signal on error
do forever
    'READTO record'		/* don't mind delay */
    parse var record sc +1 vn (sc) sv
    if pos(sc, "* ") > 0,	/* see the COMMENT option */
     then iterate
    upper vn			/* optional, see also varload */
    dummy = value(vn, sv, ...)	/* for variable pool of caller */
end
error:; exit rc * (rc <> 12)	/* or whatever rc is OK */

Well, I hope NetRexx Pipelines allows home-made stages like this.
Maybe this "take in INI file" pipe could then look something like:

NetRexx Pipe "<" fn "|varload symbolic"

(see the differences in the defaults of varset and varload.)

Best,
M.

[netrexx-pipelines] NetRexx llist works different than expected

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

Hi!

I am quite sure, it ain't my fault, it's NetRexx list what works
different than I'm used from CMS-PIPELINES list. Without a closer
look to the address fields I pressed all the time 'reply' or
'reply all' and assumed it would show up on the NetRexx-pipelines
list. Alas no.

Now I have replied to a mail from Jason Martin inadvertently with
no copy to NetRexx-pipelines, same time I find on the internet
site "netrexx-pipelines Mailing List for NetRexx" an answer from
René which did not show up in my email since hours now. Almost
impossible to reply because the sourceforge list does not offer a
reply button. (I'll copy what's important to a reply by mail.)

Sorry if it's me causing useless trouble.
M.

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

[René J. <rvj...@xs...>]

Hi Mike,

> On 2 Jun 2022, at 17:21, hp...@we... wrote:
> 
> Following append bounced,
> 
>> reason: 550 Blacklisted file extension detected
> 
> So once more without the ZIP -- René, IMO you got it in your
> personal mail, holler if not.
> /M.
> 
I have it.

> Am 02.06.2022 um 14:58 schrieb hp...@we...:
>> Hello René!
>> 
>> In chapter 3.4 of the NetRexx QuickStart Guide the shown subdir
>> separator is a "normal" slash (/) while Windows uses instead the
>> backslash (\). Must I convert it to slash or may it stay as is?
>> 

Windows normally uses a backslash and it is safe to use a backslash. In lots of circumstances a normal slash can be used (Cygwin, m2sys, Git bash etc), but standard operating procedure is using ‘\' and ‘;’ where the Unix/Linux/Mac separators are ‘/‘ and ‘:’. The slash is mentioned in note 12 on page 21. The semicolon/colon issue is already mentioned in read.me <http://read.me/>.first, line 45. 

>> Step 3 in same chapter advices to add another path+fileID to the
>> CLASSPATH variable. Alas it does not mention if and if yes how to
>> separate the two data, by blank, by semicolon, or something else?
>> 

In the read.me <http://read.me/>.first, line 45. I can add it one more time to the installation chapter.

>> There is no file [...]/lib/tools.jar in lib subdir. There is no
>> file tools.jar in any subdir of NetRexx. There is no such file in
>> the "Java tree" (assumed this is the installation folder). So
>> chapter 3.4 step 3 remains undone (until further advice).

You have a point there, as this used to be correct but in modern java versions it is optional, or better put: obsolete. I have removed it but left it in the ’Troubleshooting’ chapter.

>> 
>> NetRexx QuickStart Guide chapter 3.5, Installing just the NetREXX
>> Runtime, second paragraph states "To do this, follow the
>> appropriate instructions for installing the compiler, ..." Where
>> do I find the appropriate instructions for installing the
>> compiler? Under 3 "Installation" there is just 3.4 "Installing the
>> NetREXX Translator" and 3.5 "Installing just the NetREXX Runtime",
>> but nothing like "Installing the Compiler". Or was the compiler
>> renamed to "translator"? Pls advice.
>> 
>> NetRexx QuickStart Guide chapter 3.7 "Testing the NetREXX
>> Installation", step 1, the command
>> 

This is what happened: ’Translator’ is the supertype of ‘Compiler’ and ‘Interpreter’ here. NetRexx started out being a translator that also did compiling to .class files after translation (NetRexx source to Java source). Later an interpreter was added. (The 'nrc -exec’ or ‘-args’ part). You can also use the NetRexx runtime in any Java program (if you like substr() and pos() and value() like we do). In this case you want to instal only the runtime (well, 20 years ago on much smaller systems you would have wanted that. Nowadays really nobody cares). So you could have skipped the whole paragraph. 


>>> java org.netrexx.process.NetRexxC hello
>> 
>> fails. Closing the cmd window and starting a new one cures it.
>> Seems changing the CLASSPATH variable needs kind of power-cycle.
>> Alas...
>> 

That is a platform thing. I always just ’source’ my zshrc but then again I am on macOS, Linux or z/OS USS most of the day.

>>> Program hello.nrx
>>>  1 +++ say ?hello, world?
>>>    +++     ^
>>>    +++ Error: Unexpected character found in source: '?'
>>> (hexadecimal encoding: 2
>>> 019)
>>> Compilation of 'hello.nrx' failed [one error]
>> 
>> Again a 'nonconformance' by edit-copy/edit-paste from Adobe. (BTW,
>> there are some places in the QuickStart Guide where it works.)
>> 
Is this in the new version of the manual also?

>> Same chapter. After step 1 worked, at least last line showed
>> 
>>> Compilation of 'hello.nrx' successful
>> 
>> and there is now a file hello.class in the subdir, step 2 fails:
>> 
>>> Fehler: Hauptklasse hello konnte nicht gefunden oder geladen werden


>> Chapter 13 "Troubleshooting" reveals, CLASSPATH variable must
>> contain a point. I prefix its content by '.;' (w/o quotes)
>> _assuming_ the semicolon could be the correct delimiter. Closing
>> the cmd window, starting a new one, now step 2 of chapter 3.7
>> works right away.
>> 
>> Recently you said,
>> 

That is correct, and only for classes that are not in a package. Glad you found the ’troubleshooting’ chapter, but the examples on pages 20 and 21 have the dot in them.


>>> NetRexx does not have an ‘installation procedure’ as such...
>> 
>> Well, since the NetRexx 'installation' seems a bit more than just
>> to unpack a zip file, it could help a lot. Frankly, at the moment
>> I have some trouble to stay polite. This kind of installation
>> instruction with its widely distributed information is quite
>> unpleasant. For sure not a smooth cakewalk.

I appreciate the effort. Still, it is true that NetRexx does not have an installation procedure; it just follows the platform and java conventions. Sometimes you have to edit a profile exec, sometimes you need to concatenate a library to ISPLLIB, sometimes a PATH must be added. In Java most of the time a CLASSPATH must be there. Although, you can set it in scripts etc. Sun has transmitted mixed signals about this. We used to have this big problem that Java could not find its own compiler classes (the obsolete step 3) but we countered that by packaging a java compiler with NetRexxF.jar. And the compiler (the translator actually) does a lot of searching while trying to find which java compiler to use.

I have thought about an approach where we use the layout of the distribution to set CLASSPATH in the scripts: nrc, NetRexxC.sh, nrc.bat etcetera. In my opinion, this would shift the trouble spot to the first time someone needs to add a jar, tries to compile a program in a package, etc. 

It might have been less than pleasant, but you got it to run! I’ll try to address some of the things in your remarks to the documentation to be on the safe side.

>> 
>> Ok, I now made my way through chapter 3 of the QuickStart Guide.
>> Is there more in it I need to know/install/observe for running
>> pipelines? I continue with next "little setup", chapter 3.1 of
>> NetRexx Pipelines Guide and Reference.
>> 
>> Seems as Windows user I should read this bottom-up, then I have to
>> do nothing since NetREXXF.jar is prefixed to the CLASSPATH content
>> in pipe.bat as in pipc.bat too. Both are in the bin subdir which I
>> added to the path yesterday. But (!) I renamed PIPE.BAT to
>> HIPE.BAT to avoid interference with OS/2 Pipelines (which I
>> currently _do not_ uninstall). Do you see more pitfalls in this
>> respect?
>> 
>> Test:
>> 
>>> C:\prgm\NetRexx>hipe "gen 100 | dup 999 | count words | console
>>> 100000
>> 
>> Works :)
>> 

Yes, good result. And if you have the dot in CLASSPATH, you can at least run your own stages from their own directory. 
I would suggest to use ’nrws’ (the Netrexx Workspace) for experiments with pipes. You can leave out the quotes there, and it is a lot faster after it load the pipes machinery for the first time.

>> So it seems I have done all preparations (at last) to start our
>> experiment. Did I miss something? Yes, up to now you only have the
>> source file and a description in brief. There are few more files
>> you need to run VilMA. Find attached a ZIP with all you need in
>> case you have OS/2 Pipelines. It also contains (besides a compiled
>> ooRexx) a more detailed description about what to do with VilMA.
>> 
>> I suggest I copy my program to a new directory and replace
>> pipeline by pipeline according your advice until all are done.
>> Because I renamed pipe.bat a coexistence of NetRexx- and OS/2
>> Pipelines might be possible and therefore also an incomplete
>> migration could work as usual.
>> 
Seems like an excellent plan.


>> /M.
> 

René.

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

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

Following append bounced,

> reason: 550 Blacklisted file extension detected

So once more without the ZIP -- René, IMO you got it in your
personal mail, holler if not.
/M.

Am 02.06.2022 um 14:58 schrieb hp...@we...:
> Hello René!
>
> In chapter 3.4 of the NetRexx QuickStart Guide the shown subdir
> separator is a "normal" slash (/) while Windows uses instead the
> backslash (\). Must I convert it to slash or may it stay as is?
>
> Step 3 in same chapter advices to add another path+fileID to the
> CLASSPATH variable. Alas it does not mention if and if yes how to
> separate the two data, by blank, by semicolon, or something else?
>
> There is no file [...]/lib/tools.jar in lib subdir. There is no
> file tools.jar in any subdir of NetRexx. There is no such file in
> the "Java tree" (assumed this is the installation folder). So
> chapter 3.4 step 3 remains undone (until further advice).
>
> NetRexx QuickStart Guide chapter 3.5, Installing just the NetREXX
> Runtime, second paragraph states "To do this, follow the
> appropriate instructions for installing the compiler, ..." Where
> do I find the appropriate instructions for installing the
> compiler? Under 3 "Installation" there is just 3.4 "Installing the
> NetREXX Translator" and 3.5 "Installing just the NetREXX Runtime",
> but nothing like "Installing the Compiler". Or was the compiler
> renamed to "translator"? Pls advice.
>
> NetRexx QuickStart Guide chapter 3.7 "Testing the NetREXX
> Installation", step 1, the command
>
>> java org.netrexx.process.NetRexxC hello
>
> fails. Closing the cmd window and starting a new one cures it.
> Seems changing the CLASSPATH variable needs kind of power-cycle.
> Alas...
>
>> Program hello.nrx
>>  1 +++ say ?hello, world?
>>    +++     ^
>>    +++ Error: Unexpected character found in source: '?'
>> (hexadecimal encoding: 2
>> 019)
>> Compilation of 'hello.nrx' failed [one error]
>
> Again a 'nonconformance' by edit-copy/edit-paste from Adobe. (BTW,
> there are some places in the QuickStart Guide where it works.)
>
> Same chapter. After step 1 worked, at least last line showed
>
>> Compilation of 'hello.nrx' successful
>
> and there is now a file hello.class in the subdir, step 2 fails:
>
>> Fehler: Hauptklasse hello konnte nicht gefunden oder geladen werden
>
> Chapter 13 "Troubleshooting" reveals, CLASSPATH variable must
> contain a point. I prefix its content by '.;' (w/o quotes)
> _assuming_ the semicolon could be the correct delimiter. Closing
> the cmd window, starting a new one, now step 2 of chapter 3.7
> works right away.
>
> Recently you said,
>
>> NetRexx does not have an ‘installation procedure’ as such...
>
> Well, since the NetRexx 'installation' seems a bit more than just
> to unpack a zip file, it could help a lot. Frankly, at the moment
> I have some trouble to stay polite. This kind of installation
> instruction with its widely distributed information is quite
> unpleasant. For sure not a smooth cakewalk.
>
> Ok, I now made my way through chapter 3 of the QuickStart Guide.
> Is there more in it I need to know/install/observe for running
> pipelines? I continue with next "little setup", chapter 3.1 of
> NetRexx Pipelines Guide and Reference.
>
> Seems as Windows user I should read this bottom-up, then I have to
> do nothing since NetREXXF.jar is prefixed to the CLASSPATH content
> in pipe.bat as in pipc.bat too. Both are in the bin subdir which I
> added to the path yesterday. But (!) I renamed PIPE.BAT to
> HIPE.BAT to avoid interference with OS/2 Pipelines (which I
> currently _do not_ uninstall). Do you see more pitfalls in this
> respect?
>
> Test:
>
>> C:\prgm\NetRexx>hipe "gen 100 | dup 999 | count words | console
>> 100000
>
> Works :)
>
> So it seems I have done all preparations (at last) to start our
> experiment. Did I miss something? Yes, up to now you only have the
> source file and a description in brief. There are few more files
> you need to run VilMA. Find attached a ZIP with all you need in
> case you have OS/2 Pipelines. It also contains (besides a compiled
> ooRexx) a more detailed description about what to do with VilMA.
>
> I suggest I copy my program to a new directory and replace
> pipeline by pipeline according your advice until all are done.
> Because I renamed pipe.bat a coexistence of NetRexx- and OS/2
> Pipelines might be possible and therefore also an incomplete
> migration could work as usual.
>
> /M.

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

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

Hello René!

In chapter 3.4 of the NetRexx QuickStart Guide the shown subdir
separator is a "normal" slash (/) while Windows uses instead the
backslash (\). Must I convert it to slash or may it stay as is?

Step 3 in same chapter advices to add another path+fileID to the
CLASSPATH variable. Alas it does not mention if and if yes how to
separate the two data, by blank, by semicolon, or something else?

There is no file [...]/lib/tools.jar in lib subdir. There is no
file tools.jar in any subdir of NetRexx. There is no such file in
the "Java tree" (assumed this is the installation folder). So
chapter 3.4 step 3 remains undone (until further advice).

Chapter 3.5, Installing just the NetREXX Runtime, second paragraph
states "To do this, follow the appropriate instructions for
installing the compiler, ..." Where do I find the appropriate
instructions for installing the compiler? Under 3 "Installation"
there is just 3.4 "Installing the NetREXX Translator" and 3.5
"Installing just the NetREXX Runtime", but nothing like
"Installing the Compiler". Or was the compiler renamed to
"translator"? Pls advice.

/M.

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

[Jason M. <agr...@gm...>]

Thank you, I am to tired to do or even think about.

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

[René J. <rvj...@xs...>]

I will do that. 

@Mike: In the meantime, there is an updated Quickstart Guide at https://www.netrexx.org/documents/NetRexx%204.02-GA%20QuickStart%20Guide.pdf

most if not all examples should paste much better now.

René.


> On 2 Jun 2022, at 12:44, Jason Martin <agr...@gm...> wrote:
> 
> 
> From :
> 
> https://stackoverflow.com/questions/3001177/how-do-i-grep-for-all-non-ascii-characters
> 
> In the documentation directory to verify what remains that truly needs fixing.
> 
> pcregrep -r --color='auto' -n '[^\x00-\x7F]' .
> 
> 
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

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

[Jason M. <agr...@gm...>]

 From :

https://stackoverflow.com/questions/3001177/how-do-i-grep-for-all-non-ascii-characters

In the documentation directory to verify what remains that truly needs 
fixing.

pcregrep -r --color='auto' -n '[^\x00-\x7F]' .

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

[René J. <rvj...@xs...>]

The quotes situation was fixed earlier, so everything in an lstlisting environment block has the right, pasteable quotes.
Unfortunately, not all source is in these blocks yet. So p 21 of the Quickstart Guide has an example with curly quotes, which is also fixed now.
So if you are at 

say ‘hello world’

make sure these are straight quotes.

René.

> On 2 Jun 2022, at 11:54, René Jansen <rvj...@xs...> wrote:
> 
> After trying lots of latex environments like verbatim, listings, lists and blocks, it came out that the wrong hyphen was in the *actual document source code*. As this has been converted from OS/2 to Windows to Mac and from GML to OpenOffice and LaTeX this is no big surprise. Thanks for finding it. Fixed in NetRexx 4.04.
> 
> And yes, we need to clean those things out. For the later examples, I have them in separate files and I start a bash subprocess to make sure the examples actually work. These are easy to check, but when in the document source code this is harder. I have a longer term plan to have most of the source in Markdown, so we can use pandoc to translate to LaTeX and also have html and/or eBooks in addition to the PDF. That transition seems to be a good point to write some extra pipelines to make sure our program text is Unicode clean.
> 
> 
> René.
> 
>> On 2 Jun 2022, at 11:09, Jason Martin <agr...@gm...> wrote:
>> 
>> On 6/2/22 03:21, hp...@we... wrote:
>>> (Am I really the first who steps into this silly trap?)
>> 
>> No, there are a some idiosyncrasies when using TeX or LaTeX.
>> 
>> The one that always gets me is quoted stuff.
>> 
>> When using X Windows, I like highlighting a PDF passage and popping it to the terminal without touching the keyboard.
>> 
>> Sometimes what appears to be a quote is really another character.
>> 
>> We just need to go through our documentation's source files a little closer.
>> 
>> We could use some people who have free time to do things like that.
>> 
>> 
>> 
>> _______________________________________________
>> netrexx-pipelines mailing list
>> net...@li...
>> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines
> 
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

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

[René J. <rvj...@xs...>]

After trying lots of latex environments like verbatim, listings, lists and blocks, it came out that the wrong hyphen was in the *actual document source code*. As this has been converted from OS/2 to Windows to Mac and from GML to OpenOffice and LaTeX this is no big surprise. Thanks for finding it. Fixed in NetRexx 4.04.

And yes, we need to clean those things out. For the later examples, I have them in separate files and I start a bash subprocess to make sure the examples actually work. These are easy to check, but when in the document source code this is harder. I have a longer term plan to have most of the source in Markdown, so we can use pandoc to translate to LaTeX and also have html and/or eBooks in addition to the PDF. That transition seems to be a good point to write some extra pipelines to make sure our program text is Unicode clean.


René.

> On 2 Jun 2022, at 11:09, Jason Martin <agr...@gm...> wrote:
> 
> On 6/2/22 03:21, hp...@we... wrote:
>> (Am I really the first who steps into this silly trap?)
> 
> No, there are a some idiosyncrasies when using TeX or LaTeX.
> 
> The one that always gets me is quoted stuff.
> 
> When using X Windows, I like highlighting a PDF passage and popping it to the terminal without touching the keyboard.
> 
> Sometimes what appears to be a quote is really another character.
> 
> We just need to go through our documentation's source files a little closer.
> 
> We could use some people who have free time to do things like that.
> 
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

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

[Jason M. <agr...@gm...>]

On 6/2/22 03:21, hp...@we... wrote:
> (Am I really the first who steps into this silly trap?)

No, there are a some idiosyncrasies when using TeX or LaTeX.

The one that always gets me is quoted stuff.

When using X Windows, I like highlighting a PDF passage and popping it 
to the terminal without touching the keyboard.

Sometimes what appears to be a quote is really another character.

We just need to go through our documentation's source files a little 
closer.

We could use some people who have free time to do things like that.

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

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

Am 02.06.2022 um 02:15 schrieb hp...@we...:
> BTW, triggered by your hint elsewhere about CLASSPATH I had a look
> to the QuickStart Guide and conducted once more the simplest tests
> -- and already the first failed: java -version
> Result:
>> Fehler: Hauptklasse ?version konnte nicht gefunden oder geladen
>> werden
>
> It's so annoying, yesterday it worked. No clue how the dash
> translates to questionmark. Do I have to reinstall Java? So sad.

René!
I uninstalled Java, did a power-cycle, I installed Java and did a
power-cycle, opened a cmd window, typed 'java -version' (w/o
quotes), works. Hooray!
So I wanted to continue with chapter 3 of the QuickStart Guide,
just for fun I copied on page 19

> java –version

and pasted it to the cmd window -- and it failes:

> Fehler: Hauptklasse ?version konnte nicht gefunden oder geladen werden

So the problem was not Java, it's Adobe Acrobat what jeopardizes
edit/copy-edit/paste to the cmd window. Now nosy I did with it

> C:\prgm\NetRexx>pipe literal java -version!fblock 1!spec 1 1 1 c2x nw!term
> j 6A
> a 61
> v 76
> a 61
>   20
> û 96
> v 76
> e 65
> r 72
> s 73
> i 69
> o 6F
> n 6E

Well, seems I don't belong to the target group of this QuickStart
Guide. (Am I really the first who steps into this silly trap?)

/M.

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

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

Hello René!

Am 01.06.2022 um 19:04 schrieb René Jansen:
>> [...]
> In NetRexx, for user interfaces you mostly choose from the Java world, so Swing, AWT, SWT or JavaFx come to mind.

The plan (my plan at least) is to stay with ooRexx and replace
only OS/2 Pipelines by those of NetRexx. All what you list from
Java world is new to me.

>> It is the first time I "tele-collaborate" for programming. So I
>> have no clue what works best, one is master with the ideas and the
>> other the typist? Should we work top-down or simplest cases first,
>> the impossible later? Or do we an endless
>> question-and-answer-ping-pong?
>>
> I am a proponent of the model of sending something that works and then letting the other person go on with it. I am not afraid of endless q&a ping pong either. I would like to try the modern two-persons-in-an-edit session sometimes, but my days are not that plannable.

I'm fine with your proposal to send what works for you and I'll
try if it also works for me. That might result in some q&a. I'd
like to restrain from same-time edit sessions, I am a hobbyist and
thus there is no "pressure to success".

>> My first question would be, the "glue" code to get access to
>> pipelines is now
>>
>>> call RxFuncAdd 'RxPipe', 'RXPIPE', 'RXPIPE'
>
> In NetRexx there is no RxFuncAdd. You need to compile a class that uses pipes with the pipc compiler. There should be an alias or .bat file for that.

Q: I do stay with ooRexx, or not? I'm not going to migrate the
complete program to NetRexx, only the pipes are replaced? Just to
be sure.

> Example: [...]

I took your example to a file, named it 'fstxmp.nrx' and had to
learn, that is not possible, 'class stemtest' requires the file to
be 'stemtest.nrx'

Now nrc stemtest.nrx shows:
> java -cp ";;C:\prgm\NetRexx\lib\NetRexxF.jar;." -Dnrx.compiler=ecj org.netrexx.p
> rocess.NetRexxC  stemtest.nrx
> NetRexx portable processor 4.03-GA build 260-20220503-1730
> Copyright (c) RexxLA, 2011,2022.   All rights reserved.
> Parts Copyright (c) IBM Corporation, 1995,2008.
> Program stemtest.nrx
>  17 +++    pipe (stempipe debug 0 ) stem a | prefix literal {a} | console | stem
>  b
>     +++                                                     ^
>     +++ Error: Unexpected character found in source: '{' (hexadecimal encoding:
> 007B)
> Compilation of 'stemtest.nrx' failed [one error]

What me wonders is the hex encoding '007B'x instead of simply
'7B'x -- is that the cause of this error?

> Since NetRexx 4.03 (that is about a month)  you can also just use address and receive output in a stem:
>
> out =''
> address pipe with output stem out
> “ | split | reverse | cons"
> do i=1 to out[0]
>    say out[i]
> end

Filed this one as 'omexar.nrx' and applied 'nrc omexar.nrx', result:
> Compilation of 'omexar.nrx' successful [one warning]

It was the variable i ...
> Warning: Wrong syntax for DO; retrying as a LOOP instruction

BTW, there is no need any more to have within the first ten lines
a comment? IIRC, this was used on VM/CMS to distinguish a REXX
from EXEC2.

> This works from the normal NetRexx compiler, which most people alias to nrc.

I did it not intentionally, but it seems the installation done it
for me. At least I may use nrc as a command.

>> Does NetRexx need something similar?
>>
>> The first pipeline is to varload (or varset) the INI file:
>>
>>> fn = left(fid, lastpos('.', fid)) || 'ini'
>>> call RxPipe '< "' || fn || '"!nlocate 1 /*/!varset'

Hmm... -- do I not understand what this following three tests are.
And how I have to implement them.

> ➜  test git:(master) ✗ cat varset.nrx
> vars =''
> address pipe with output stem vars
> "< vars.ini | nlocate 1 /*/ | cons"
> do i=1 to vars[0]
>    say vars[i]
> end
>
> ➜  test git:(master) ✗ cat vars.ini
> aap = 1
> noot = 2
> * mies = 3
> wim = 4
>
> ➜  test git:(master) ✗ nrc -exec varset.nrx
> NetRexx portable processor 4.04-alpha build 272-20220524-1803
> Copyright (c) RexxLA, 2011,2022.   All rights reserved.
> Parts Copyright (c) IBM Corporation, 1995,2008.
> Program varset.nrx
> ===== Exec: varset =====
> aap = 1
> noot = 2
> wim = 4
> Processing of 'varset.nrx' complete

Could you pls explain what's my part now?

> So that does more or less what you want already - the source redirect <, the nlocate works. If you want we can make a varset stage, I think we don’t have that at the moment but it cannot be too hard.

Varset or varload not yet available? That's a nice way to set some
defaults like:

> *
> ***  VilMA.ini - set defaults to your gusto
> *
> * where to file VilMA lists
> /VIMDR/C:\prgm\rexx\VilMA\
> *
> * mostly used directory for controller state files
> /CTLDR/C:\prgm\HP-Emulators\V41\
> *
> * mostly used VIL file location
> /VILDR/C:\prgm\HP-Emulators\VirtIL\
> *
> * Port number increment
> /DELTA/3
> *
> * Initial VILMA list to use at every start
> */ITLVL/VOID
> /ITLVL/std.vilma
> *
> * File-ID of controllers list
> /CTRLS/VILMA.Controllers
> *
> * File-ID of programs' caption
> /TPCPT/typical.caption
> *
> * dialog position, pixels 'left top' from screen border
> /DiaPos/321 23
> * trace execution
> */pst.8/1

I assume you have access to "the Book", so I don't need to explain
any details.

BTW, triggered by your hint elsewhere about CLASSPATH I had a look
to the QuickStart Guide and conducted once more the simplest tests
-- and already the first failed: java -version
Result:
> Fehler: Hauptklasse ?version konnte nicht gefunden oder geladen werden

It's so annoying, yesterday it worked. No clue how the dash
translates to questionmark. Do I have to reinstall Java? So sad.

Best,
M.

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

[René J. <rvj...@xs...>]

Hi Mike,

> On 31 May 2022, at 22:51, hp...@we... wrote:
> 
> Hello René!
> 
> Thank you for your kind offer to give it a try to convert my
> little toy to NetRexx Pipelines.
> 
> I guess the "main" routine will remain an ooRexx program since I
> use ooDialog for the Windows drudgery (or has NetRexx something
> better for dialog windows?) So the task is "only" to get rid of
> everything OS/2 Pipelines and redo it with something I have no
> idea yet.

In NetRexx, for user interfaces you mostly choose from the Java world, so Swing, AWT, SWT or JavaFx come to mind.

> 
> It is the first time I "tele-collaborate" for programming. So I
> have no clue what works best, one is master with the ideas and the
> other the typist? Should we work top-down or simplest cases first,
> the impossible later? Or do we an endless
> question-and-answer-ping-pong?
> 
I am a proponent of the model of sending something that works and then letting the other person go on with it. I am not afraid of endless q&a ping pong either. I would like to try the modern two-persons-in-an-edit session sometimes, but my days are not that plannable.

> My first question would be, the "glue" code to get access to
> pipelines is now
> 
>> call RxFuncAdd 'RxPipe', 'RXPIPE', 'RXPIPE'

In NetRexx there is no RxFuncAdd. You need to compile a class that uses pipes with the pipc compiler. There should be an alias or .bat file for that.
Example:

class stemtest

method stemtest()

   a = Rexx 'abase'
   b = Rexx 1

   a[0]=5
   a[1]=11
   a[2]=222
   a[3]=3333
   a[4]=444
   a[5]=55

   pipe (stempipe debug 0 ) stem a | prefix literal {a} | console | stem b

   loop i=1 to b[0]
      say 'b['i']='b[i]
   end


method main(a=String[]) static

   stemtest()
   exit


Since NetRexx 4.03 (that is about a month)  you can also just use address and receive output in a stem:

out =''
address pipe with output stem out
“ | split | reverse | cons"
do i=1 to out[0]
  say out[i]
end

This works from the normal NetRexx compiler, which most people alias to nrc.


> 
> Does NetRexx need something similar?
> 
> The first pipeline is to varload (or varset) the INI file:
> 
>> fn = left(fid, lastpos('.', fid)) || 'ini'
>> call RxPipe '< "' || fn || '"!nlocate 1 /*/!varset'

➜  test git:(master) ✗ cat varset.nrx
vars =''
address pipe with output stem vars
"< vars.ini | nlocate 1 /*/ | cons"
do i=1 to vars[0]
  say vars[i]
end

➜  test git:(master) ✗ cat vars.ini
aap = 1
noot = 2
* mies = 3
wim = 4

➜  test git:(master) ✗ nrc -exec varset.nrx
NetRexx portable processor 4.04-alpha build 272-20220524-1803
Copyright (c) RexxLA, 2011,2022.   All rights reserved.
Parts Copyright (c) IBM Corporation, 1995,2008.
Program varset.nrx
===== Exec: varset =====
aap = 1
noot = 2
wim = 4
Processing of 'varset.nrx' complete

So that does more or less what you want already - the source redirect <, the nlocate works. If you want we can make a varset stage, I think we don’t have that at the moment but it cannot be too hard.

René.
 

> 
> Let's take this as a first try. When it works the rest should also
> be doable.
> 
> Best,
> M.
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines

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

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

Hello René!

Thank you for your kind offer to give it a try to convert my
little toy to NetRexx Pipelines.

I guess the "main" routine will remain an ooRexx program since I
use ooDialog for the Windows drudgery (or has NetRexx something
better for dialog windows?) So the task is "only" to get rid of
everything OS/2 Pipelines and redo it with something I have no
idea yet.

It is the first time I "tele-collaborate" for programming. So I
have no clue what works best, one is master with the ideas and the
other the typist? Should we work top-down or simplest cases first,
the impossible later? Or do we an endless
question-and-answer-ping-pong?

My first question would be, the "glue" code to get access to
pipelines is now

> call RxFuncAdd 'RxPipe', 'RXPIPE', 'RXPIPE'

Does NetRexx need something similar?

The first pipeline is to varload (or varset) the INI file:

> fn = left(fid, lastpos('.', fid)) || 'ini'
> call RxPipe '< "' || fn || '"!nlocate 1 /*/!varset'

Let's take this as a first try. When it works the rest should also
be doable.

Best,
M.

Re: [netrexx-pipelines] The link to NetRexx Forums is broken.

[René J. <rvj...@xs...>]

Not new, working on that. I had it under Cloudflare for a moment until I realized that with the free version lots of ports are closed; but then https *was* working. It needs to go to the RexxLA server any day now, which will fix it.

Best regards,

René.

> On 31 Jan 2022, at 11:55, Marc Remes <re...@gm...> wrote:
> 
> And for the record: https://www.netrexx.org is not responding, http:// is.
> Not sure if this is new however..
> 
> [~]$ wget https://www.netrexx.org
> --2022-01-31 11:50:51--  https://www.netrexx.org/
> Resolving www.netrexx.org (www.netrexx.org)... 54.161.20.82
> Connecting to www.netrexx.org (www.netrexx.org)|54.161.20.82|:443... failed: Connection timed out.
> Retrying.
> 
> --2022-01-31 11:53:02--  (try: 2)  https://www.netrexx.org/
> Connecting to www.netrexx.org (www.netrexx.org)|54.161.20.82|:443... ^C
> 
> [~]$ wget http://www.netrexx.org
> --2022-01-31 11:53:16--  http://www.netrexx.org/
> Resolving www.netrexx.org (www.netrexx.org)... 54.161.20.82
> Connecting to www.netrexx.org (www.netrexx.org)|54.161.20.82|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 6101 (6.0K) [text/html]
> Saving to: ‘index.html’
> 
> index.html 100%[====================================================================================================>]   5.96K --.-KB/s    in 0.001s
> 
> 2022-01-31 11:53:16 (4.66 MB/s) - ‘index.html’ saved [6101/6101]
> 
> Marc
> 
>> On 1/31/22 11:10, René Jansen wrote:
>> Hi Leslie,
>> Thanks for bringing this to my attention. It is fixed now.
>> Best regards,
>> René.
>>>> On 31 Jan 2022, at 08:17, J Leslie Turriff <jlt...@ma...> wrote:
>>> 
>>> Hi,
>>>    At the https://www.netrexx.org/ website, the link to NetRexx Forum returns a Server Not
>>> Found page:
>>> | http://ibm-netrexx.215625.n3.nabble.com/
>>> | Hmm. We’re having trouble finding that site.
>>> |
>>> | We can’t connect to the server at ibm-netrexx.215625.n3.nabble.com.
>>> |
>>> | If that address is correct, here are three other things you can try:
>>> |
>>> |     Try again later.
>>> |     Check your network connection.
>>> |     If you are connected but behind a firewall, check that Waterfox has permission to
>>> access the Web.
>>> 
>>> Leslie
>>> --
>>> Platform: Linux
>>> Distribution: openSUSE Leap 15.3 x86_64
>>> 
>>> java version "17" 2021-09-14 LTS
>>> Java(TM) SE Runtime Environment (build 17+35-LTS-2724)
>>> Java HotSpot(TM) 64-Bit Server VM (build 17+35-LTS-2724, mixed mode, sharing)
>>> 
>>> NetRexx portable processor 4.02-GA build 55-20220124-1319
>>> 
>>> Waterfox Limited Waterfox G4.0.6
>>> 
>>> 
>>> _______________________________________________
>>> netrexx-pipelines mailing list
>>> net...@li...
>>> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines
>> _______________________________________________
>> netrexx-pipelines mailing list
>> net...@li...
>> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines