Menu
▾
▴
[netrexx-pipelines] New NetRexx Pipelines Stage: ALL
|
From: Jeff H. <Je...@Je...> - 2023-01-11 02:15:55
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I have finally added the <b>ALL</b> stage to NetRexx Pipelines.</p>
<p>This almost matches the CMS Pipelines version, except for some
symbol notation. NetRexx & Pipelines "eat" the "|" and "("
& ")" before the stage gets to see them. So, for OR use "!"
and for grouping use "[" and "]". IBM uses the 3270's "¬" for
NOT, here KEX's "^" or NetRexx's own "\" -- but it needs to be
doubled up as "\\" -- also work.</p>
<p>The internal logic of CMS is to construct a new sub-pipe with
LOCATE and NLOCATE stages; NetRexx simply uses the logic handling
built into NetRexx. This is noticeable in the output of %debug
and %dump options.<br>
</p>
<p>There are also confirmation tests, and the HTML Stages file has
been updated with this. That file now also has the ability to
show only the changes by version number (4.05, 3.11, and 3.09). <br>
</p>
<p>This update has been pushed for the next NetRexx release.</p>
<p>[I think this completes all the major stages from CMS that need
to be in NetRexx.]</p>
<p>Jeff</p>
<table>
<tbody>
<tr class="c405" style="">
<td class="name"><span id="all">all
<br>
<span class="n405">
</span></span></td>
<td class="desc">Select Lines Containing Strings (or Not)
<div>
<div class="p-ddiv">
<div class="p-diag box">
<font face="monospace">▶▶--ALL---+----------+--|
expression |---▶◄ <br>
</font></div>
<div class="p-diag box"><font face="monospace">
+--%debug--+ (6) <br>
</font></div>
<div class="p-diag box"><font face="monospace">
+--%dump---+ (7)
</font></div>
</div>
<div class="p-note">
Notes:
<ul>
<li>(1) "expression" consists of one or more
delimitedstrings separated by logical ANDs, ORs, and
NOTs, and grouped, if needed, by parentheses.
</li>
<li>(2) "&" is used for AND.
</li>
<li>(3) Since "|" is the default stage separator, "!"
may be used for OR.
</li>
<li>(4) Since NetRexx uses "(" and ")" for options --
which are not used in the ALL stage -- "[" and "]"
must be used for parentheses.
</li>
<li>(5) CMS Pipelines, having originated on 3270
terminals, uses "¬" for NOT. This symbol is not
readily typed on terminals running NetRexx
Pipelines, so as alternatives, "\\", used by
NetRexx, (it needs to be doubled to "escape" it) or
"^", used by KEX, NOT symbols may be used as
alternatives.
</li>
<li>(6) %debug (must be lowercase) NetRexx Pipelines
writes the logic line to the file ALL.DEBUG in the
current directory. Windows may make it all.debug .
CMS Pipelines writes the constructed pipeline (of
LOCATE and NLOCATE stages) to ALL DEBUG A.
</li>
<li>(7) %dump (must be lowercase) - writes to the
primary output stream as the first record. NetRexx
Pipelines writes the logic line. CMS Pipelines
writes constructed pipeline.
</li>
<li>CMS Pipelines uses is own logic order. NetRexx
Pipelines uses regular NetRexx
</li>
</ul>
Examples:
<ul>
<li class="examp"> literal NetRexx is Good,NetRexx is
Great,NetRexx is Fantastic |
<br>
split , |
<br>
<span class="red">all /a/</span> |
<br>
cons
<br>
<br>
▶NetRexx is Great
<br>
▶NetRexx is Fantastic
<br>
</li>
<li class="examp">
literal NetRexx is Good,NetRexx is Great,NetRexx is
Fantastic |
<br>
split , |
<br>
<span class="red">all / G/ & [/oo/ ! /F/]</span>
|
<br>
cons
<br>
<br>
▶NetRexx is Good
<br>
</li>
<li class="examp">
literal NetRexx is Good,NetRexx is Great,NetRexx is
Fantastic |
<br>
split , |
<br>
<span class="red">all /R/ & [/oo/ ! /F/]</span>
|
<br>
cons
<br>
<br>
▶NetRexx is Good
<br>
▶NetRexx is Fantastic
</li>
</ul>
</div>
</div>
</td>
</tr>
</tbody>
</table>
</body>
</html>
|
