Menu
▾
▴
Re: [netrexx-pipelines] [oorexx:discussion] CMS Pipelines implementations
|
From: Jeff H. <Je...@Je...> - 2021-08-19 12:39:46
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>[still crossposted]</p>
<p>M-stgt,</p>
<p>The <a moz-do-not-send="true" href="http://netrexx.org/">NetRexx</a>
implementation is a nearly complete, and extended, version of CMS
Pipelines and is usable today. For documentation of the program
and all the included stages, highlighting the differences from the
CMS implementation, see <b><a moz-do-not-send="true"
href="http://netrexx.org/documents/NetRexx%204.01-GA%20Pipelines%20Guide%20and%20Reference.pdf">Pipelines
Guide and Reference</a></b>. Most of the differences are due
to CMS-only stages and options dealing with IBM only, or now
obsolete, things, and Java/PC additions. <br>
</p>
<p>
<blockquote type="cite"><span style="left: 151.2px; top:
161.731px; font-size: 23.9103px; font-family: serif;
transform: scaleX(1.30166);" role="presentation" dir="ltr">20</span><br
role="presentation">
<span style="left: 151.2px; top: 228.555px; font-size:
34.4375px; font-family: serif; transform: scaleX(1.24191);"
role="presentation" dir="ltr">Differences with CMS Pipelines</span><br
role="presentation">
<span style="left: 151.2px; top: 324.123px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.14261);"
role="presentation" dir="ltr">The goal of this implementation
is to be as close as possible to the the CMS</span><br
role="presentation">
<span style="left: 151.2px; top: 347.368px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.07942);"
role="presentation" dir="ltr">version of Pipelines. A few
differences are unavoidable.</span><br role="presentation">
<span style="left: 173.255px; top: 364.024px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 364.024px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 383.898px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.09258);"
role="presentation" dir="ltr">The character set is Unicode and
not EBCDIC, as Unicode is the character</span><br
role="presentation">
<span style="left: 192.712px; top: 407.144px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.10448);"
role="presentation" dir="ltr">set of the underlying Java
platform</span><br role="presentation">
<span style="left: 173.255px; top: 412.593px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 412.593px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 432.466px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.10212);"
role="presentation" dir="ltr">As shells are different, many
3270 related stages are not implemented</span><br
role="presentation">
<span style="left: 173.255px; top: 437.914px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 437.914px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 457.788px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.15048);"
role="presentation" dir="ltr">Pipes need to be quoted on the
Windows and Unix command lines; the</span><br
role="presentation">
<span style="left: 192.712px; top: 481.034px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.0327);"
role="presentation" dir="ltr">Workspace for NetREXX (</span><span
style="left: 415.535px; top: 481.034px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.186);"
role="presentation" dir="ltr">nrws</span><span style="left:
461.438px; top: 481.034px; font-size: 19.9253px; font-family:
serif; transform: scaleX(1.10514);" role="presentation"
dir="ltr">) environment is an exception to this rule</span><br
role="presentation">
<span style="left: 173.255px; top: 486.481px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 486.481px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 506.356px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.09766);"
role="presentation" dir="ltr">The mainframe is record-oriented
in many stages, Pipelines for NetREXX</span><br
role="presentation">
<span style="left: 192.712px; top: 529.601px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.10617);"
role="presentation" dir="ltr">does an approximation of this</span><br
role="presentation">
<span style="left: 173.255px; top: 535.049px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 535.049px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 554.923px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.09542);"
role="presentation" dir="ltr">Pipelines on the mainframe is an
interpreted language with components as</span><br
role="presentation">
<span style="left: 192.712px; top: 578.169px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.10892);"
role="presentation" dir="ltr">the scanner and the dispatcher;
the NetREXX version is compiled to Java</span><br
role="presentation">
<span style="left: 192.712px; top: 601.416px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.08608);"
role="presentation" dir="ltr">.class files by</span><span
style="left: 309.873px; top: 601.416px; font-size: 19.9253px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 316.522px; top: 601.416px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.10807);"
role="presentation" dir="ltr">pipc</span><span style="left:
354.523px; top: 601.416px; font-size: 19.9253px; font-family:
serif; transform: scaleX(1.14906);" role="presentation"
dir="ltr">, the pipes compiler, and dispatched as threads by
the</span><br role="presentation">
<span style="left: 192.712px; top: 624.661px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.05962);"
role="presentation" dir="ltr">JVM.</span><br
role="presentation">
<span style="left: 173.255px; top: 630.109px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 630.109px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 649.983px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.17187);"
role="presentation" dir="ltr">The mainframe pipes dispatcher
is not multiprocessor enabled. In Pipelines</span><br
role="presentation">
<span style="left: 192.712px; top: 673.229px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.08353);"
role="presentation" dir="ltr">for NetREXX all tasks (stages)
are dispatched over all available processors</span><br
role="presentation">
<span style="left: 192.712px; top: 696.476px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.10521);"
role="presentation" dir="ltr">in parallel.</span><br
role="presentation">
<span style="left: 173.255px; top: 701.924px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 701.924px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 721.798px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.0674);"
role="presentation" dir="ltr">The fact that pipes run from
NetREXX implies that they can be used in Java</span><br
role="presentation">
<span style="left: 192.712px; top: 745.044px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.09043);"
role="presentation" dir="ltr">source. In previous releases
there was more direct support for this; this has</span><br
role="presentation">
<span style="left: 192.712px; top: 768.289px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.09952);"
role="presentation" dir="ltr">lapsed due to changes in the way
a java toolchain works. This support can</span><br
role="presentation">
<span style="left: 192.712px; top: 791.536px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.11264);"
role="presentation" dir="ltr">be restored in future releases.</span><br
role="presentation">
<span style="left: 173.255px; top: 796.984px; font-size:
41.3118px; font-family: serif;" role="presentation" dir="ltr">.</span><span
style="left: 184.409px; top: 796.984px; font-size: 41.3118px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 192.712px; top: 816.858px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.14365);"
role="presentation" dir="ltr">To put the content of a NetREXX
variable in a pipe specification in a NetREXX</span><br
role="presentation">
<span style="left: 192.712px; top: 840.104px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.10332);"
role="presentation" dir="ltr">program, there is a</span><span
style="left: 357.474px; top: 840.104px; font-size: 19.9253px;
font-family: serif;" role="presentation" dir="ltr"> </span><span
style="left: 361.752px; top: 843.284px; font-size: 16.3388px;
font-family: monospace; transform: scaleX(1.00119);"
role="presentation" dir="ltr">{}</span><span style="left:
381.358px; top: 843.284px; font-size: 16.3388px; font-family:
monospace;" role="presentation" dir="ltr"> </span><span
style="left: 385.632px; top: 840.104px; font-size: 19.9253px;
font-family: serif; transform: scaleX(1.08315);"
role="presentation" dir="ltr">mechanism. In CMS the pipe would
be quoted in the</span><br role="presentation">
<span style="left: 192.712px; top: 863.349px; font-size:
19.9253px; font-family: serif; transform: scaleX(1.08667);"
role="presentation" dir="ltr">Rexx source and you would
unquote sections to get a similiar effect.</span></blockquote>
There are some additional "goodies" too. For example, because of
NetRexx's dual Rexx and Java influences, in addition to the CMS
Pipelines <b>CHANGE</b> stage using XEDIT syntax, there are new
stages: <b>CHANGEPARSE</b> that uses Rexx PARSE syntax and <b>CHANGEREGEX</b>
that uses Java regular expressions syntax. The second half of the
Guide and Reference documents all the stages in both CMS and
NetRexx versions, with color highlighted differences.<br>
</p>
<p>And, of course, it is all open source, so if there is something
you need and not yet implemented, please do it and submit it.
Thanks!</p>
<p>Jeff<br>
</p>
<div class="moz-cite-prefix">On 8/19/2021 6:10 AM, René Jansen
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:569...@xs...">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
[changed subject line and crossposted]
<div class=""><br class="">
</div>
<div class="">Pipelines for NetRexx strives to be an exactly
compatible, and as complete as possible implementation of CMS
Pipelines. As this is off-topic for oorexx I crossposted to the
pipelines-netrexx list where I can answer any question you might
have!</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class=""><br class="">
</div>
<div class="">René.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 19 Aug 2021, at 12:04, m-stgt <<a
href="mailto:m-...@us..." class=""
moz-do-not-send="true">m-...@us...</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="markdown_content">
<p class="">Ok, little subject drift -- Gil Barmwater
and Erich, hello!<br class="">
I know there are two..three efforts, maybe four, to
get a copy of CMS Pipelines running on PCs. But likely
I do wrong expecting it could ever be as complete as
the role model. Just have a look at <a class=""
href="http://vm.marist.edu/%7Epipeline/pipeline.pdf"
rel="nofollow" moz-do-not-send="true">"the Book"</a>
with its nearly 1000 pages -- quite implausible this
could be rerun trouble-free and effortless on other
platforms. So I should stop complaining and live with
the availabel efforts.<br class="">
BTW, within the samples I find a pipe.rex and a
usepipe.rex but no pipe.cls -- I am still using
REXX-ooRexx_4.2.0(MT)_32-bit 6.04 22 Feb 2014.</p>
<hr class="">
<p class=""><a class=""
href="https://sourceforge.net/p/oorexx/discussion/408478/thread/a794679bb8/?limit=25#bf23/1a7b/43be/640c/a0b0"
moz-do-not-send="true">How may offspring tell parent
to do something?</a></p>
<hr class="">
<p class="">Sent from <a href="http://sourceforge.net"
class="" moz-do-not-send="true">sourceforge.net</a>
because you indicated interest in <a
href="https://sourceforge.net/p/oorexx/discussion/408478/"
class="" moz-do-not-send="true">https://sourceforge.net/p/oorexx/discussion/408478/</a></p>
<p class="">To unsubscribe from further messages, please
visit <a
href="https://sourceforge.net/auth/subscriptions/"
class="" moz-do-not-send="true">https://sourceforge.net/auth/subscriptions/</a></p>
</div>
<div itemscope=""
itemtype="http://schema.org/EmailMessage" class="">
<div itemprop="action" itemscope=""
itemtype="http://schema.org/ViewAction" class="">
<link itemprop="url"
href="https://sourceforge.net/p/oorexx/discussion/408478/"
class="">
<meta itemprop="name" content="View" class="">
</div>
<meta itemprop="description" content="View" class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
netrexx-pipelines mailing list
<a class="moz-txt-link-abbreviated" href="mailto:net...@li...">net...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines">https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines</a>
</pre>
</blockquote>
</body>
</html>
|
