Menu
▾
▴
Re: [netrexx-pipelines] LOCATE Stage name abbreviation: No
|
From: Jeff H. <Je...@Je...> - 2022-06-29 17:06:22
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>The NetRexx Pipelines documentation does both. <br>
</p>
<p><img src="cid:par...@Je..." alt=""></p>
<p>The left shows the command and all aliases. The RRT uses UPPER
case for the required part and lower case for optional, full,
parts, following the Rexx convention.<br>
</p>
Also, the same information is duplicated under both <b>xlate</b>
and <b>translate</b> in their respective alphabetical locations.
So if you are trying to read an existing pipe that has a <b>translate</b>
stage it is easy to find. The IBM publication sometimes buries that
information in a footnote.
<p>As a further service, this alias information is extended to
stages that are CMS only:</p>
<p><img src="cid:par...@Je..." alt=""></p>
<p>Our "big problem" is using text rather than fancy illustrations
so the solid triangles are not exactly a character wide and the
back-and-down arrows don't quite meet up. Terrible!</p>
<p>The underlined parts, online, are links to popups that expand on
the definition of it, in this case, what an xrange is.</p>
<p>Jeff<br>
</p>
<div class="moz-cite-prefix">On 6/29/2022 11:42 AM, J Leslie Turriff
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:202...@ma...">
<pre class="moz-quote-pre" wrap=""> I think that part of the reason that the abbreviations are not well documented is that
the railroad track syntax diagram convention is to show the command name (here the stage
name) in all caps. This of course obscures the available abbreviations of stage names.
It would be very helpful if the title of each section that described a stage showed the
stage name in the expected abbreviation form; that way, just looking at the ToC would
make them obvious.
I don't expect to see any such change making it into the mainframe documentation,
though.)
Leslie
On 2022-06-25 20:43:15 Jeff Hennick wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">It looks like the manual is wrong here, too.
My vote is for NetRexx Pipelines to use the abbreviations, as does the
XEDIT model, and document the discrepancy. Jeff
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
--
Operating System: Linux
Distribution: openSUSE Leap 15.4 x86_64
java version "18" 2022-03-22
NetRexx portable processor 4.03-GA build 260-20220503-1730
_______________________________________________
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> |
