Menu
▾
▴
[netrexx-pipelines] LOCATE Stage name abbreviation: No
|
From: Jeff H. <Je...@Je...> - 2022-06-25 20:21:44
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Mike,</p>
<p>Right now I can not find your message dealing with the <b>LOCATE</b>
stage and, in NetRexx Pipelines, not being able to abbreviate its
name down to "L", to be able to respond to it.<br>
</p>
<p>I have just spent several hours going through the IBM <b>CMS
Pipelines User's Guide and Reference <i>Version 7 Release 1</i></b>
(which as far as I can see is the most recent) checking each
documented stage and its aliases to be sure our system matched and
was documented correctly. (The manual hides aliases in different
places for different stages and does not index them. And on some
stages puts the name in all lowercase instead of all upper.) I
found a couple of stages where we do not yet have the shortened
name aliases, and will be committing them and updated tests &
documentation soon.</p>
<p>But, <b>LOCATE</b> is not one of them. This is what the manual
has:</p>
<p><img src="cid:par...@Je..." alt=""></p>
<p>No lowercase <b>Locate</b> to indicate a short version will
work.</p>
<p>You could create your own local stage named <b>L</b> in <b>l.nrx</b>
that would call <b>LOCATE</b>, then compile it with <b>pipc</b>.
Such as this:</p>
<blockquote>
<p><font face="monospace">options nostrictcase nostrictargs
nostrictsignal<br>
import org.netrexx.njpipes.pipes.<br>
class l extends locate</font><br>
</p>
</blockquote>
<p>(I have not tried this myself.) But adding it to the release now
would likely break some existing pipes.</p>
<p>Jeff<br>
</p>
<p><br>
</p>
</body>
</html> |
