Menu
▾
▴
Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes
|
From: Jeff H. <Je...@Je...> - 2022-06-17 18:44:39
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>My ERROR! I apologize.<br>
</p>
<p>In getting NetRexx Pipelines stages updated last year, I did not
look at the working LOCATE stage, and did not inspect the IBM
documentation to see it could be abbreviated to just L. I will
supply the needed short class files (one is needed for each
"word": L, LO, LOC, etc. to call the LOCATE stage) to do this.
When I have time, I'll scan the IBM documentation to see if there
are other such stages I have missed.</p>
<p>Jeff Hennick<br>
</p>
<div class="moz-cite-prefix">On 6/14/2022 6:41 PM, <a class="moz-txt-link-abbreviated" href="mailto:hp...@we...">hp...@we...</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:753...@we...">Hi,
<br>
<br>
at least I have done the first not-for-test-only NetRexx pipe.
<br>
A very simple one, read a file, discard comments, save first
<br>
record in a variable, save rest in a stem.
<br>
<br>
Alas, some points displease:
<br>
i) the ooRexx integration per Address "" ... input ... output
<br>
force some changes, there is only one output connection possible,
<br>
but this pipe has two, a variable and a stem. Thus I had to solve
<br>
this in the post-processing.
<br>
ii) the input file consists of 10 records, 5 comment and 5 data,
<br>
what is close to nothing. Nonetheless it takes almost 1.7 seconds
<br>
to process, what is way too much for almost nothing. I hope there
<br>
is a chance to accelerate it notedly.
<br>
iii) labels require a blank after the colon,
<br>
iv) stage Locate can't be abbreviated to L, (yes, sure, this and
<br>
the point before is of minor importance, I know, but it adds to
<br>
the annoying differences to what I'm accustomed),
<br>
v) nonexistent input file ends processing of the ooRexx program
<br>
with an error. I assume this is due to the Address input/output
<br>
enclosure, Pipelines would just set the variable and the stem
<br>
accordingly.
<br>
<br>
Here what it was (set as comment) and how I replaced it:
<br>
<br>
<blockquote type="cite">-- call RxPipe '(end ?) file "' || vilif
|| '"!strip!l!nlocate 1 /*/!a:take!var conif',
<br>
-- '?a:!b:lookup 1 detail!stem livil.',
<br>
-- '?literal +-!fblock 1!b:' /* filter with lookup as
locate missing option anyof */
<br>
</blockquote>
<br>
<blockquote type="cite">f = .stream~new(vilif)
<br>
address "" ripe '"(sep ! end ?) cons',
<br>
'! strip!locate!nlocate 1 /*/',
<br>
'!a: drop!locate 1 any /+-/',
<br>
'!b: fanin!term',
<br>
'?a:!elastic!b:',
<br>
with input stream (f) output stem livil.
<br>
drop f
<br>
/* post-processing */
<br>
conif = livil.[livil.0]
<br>
livil.0 -= 1
<br>
</blockquote>
<br>
For a simpler post-processing I replaced take by drop. The changes
<br>
for a missing input file are not shown.
<br>
<br>
All suggestions for speed-up are welcome.
<br>
<br>
Best,
<br>
M.
<br>
<br>
<br>
_______________________________________________
<br>
netrexx-pipelines mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:net...@li...">net...@li...</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines">https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines</a>
<br>
</blockquote>
</body>
</html>
|
