Menu
▾
▴
Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes
|
From: Jeff H. <Je...@Je...> - 2022-06-23 02:20:25
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Leslie,</p>
<p>Thanks for your continuing input.</p>
<p>I think we already cover this. These are among the tests it
passes now (specs_tests5.njp & specs_tests6.njp):</p>
<p>-- specs "-x;-y" range ?<br>
-- specs "x.y" range ?<br>
-- specs "-x.y" range ?<br>
-- specs "-x.y" range ?<br>
-- specs "x" range ?<br>
-- specs "-x" range ?<br>
</p>
<p>-- specs "w-x;-y" range ?<br>
-- specs "w x.y" range ?<br>
-- specs "w -x.y" range ?<br>
-- specs "w -x.y (last)" range ?<br>
-- specs "w x" range ?<br>
-- specs "w -x" range ?<br>
</p>
<p>Are there some combinations that I have missed? <br>
</p>
<p>When fields are recognized, the same logic and selectors will
apply. (I am working on temporarily adding a character into each
field turning it into a bounded "word" even if it is empty, doing
the selection, then removing the character. This permits using
Rexx's wonderful word handling for fields.)</p>
<p>Please keep the comments and observations coming. I have little
real world tests to work with, and no access now to CMS for where
the documentation leaves some holes to interpret. Thank you.<br>
</p>
<p>Jeff<br>
</p>
<div class="moz-cite-prefix">On 6/22/2022 4:17 PM, J Leslie Turriff
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:202...@ma...">
<pre class="moz-quote-pre" wrap="">Jeff,
In a post to <a class="moz-txt-link-abbreviated" href="mailto:oor...@li...">oor...@li...</a>, René provided a sample pipeline to
process z/OS SMF records using the nrx specs stage. I thought you might like to be aware
of another feature of the CMS specs stage that could be incorporated into nrx specs, so
I'm sending it to you as well.
-----------
René
I see that in this pipeline you use reverse with specs to trim trailing parts of your
records. I understand that the nrx specs stage does not yet completely emulate the CMS
specs stage, but I hope that as it is improved it will fully support CMS-type inputRange
notation.
In CMS/TSO Pipelines, Author's Edition, pp. 165, 166 we see that
| "An inputRange can contain a negative number; this specifies that the count is from the
| end of the record rather than from the beginning:
| word -2 1
| The general form of a range consists of two numbers separated a semicolon. Thus, there
| is a third idiom to refer to the entire record: 1;-1. When both numbers are positive,
| there is no difference between using semicolon and using a hyphen to delimit the
numbers. When the two numbers have the same sign, the first number must be less than or
equal to the second one; it is an error to specify an ending column that is before the
beginning one. (Recall that -2 is less than -1.) When the numbers have different signs,
a null input field is used when the beginning position is after the end position:
| word 2;-2 1
Thus, your pipeline could eventually use
| :
| | specs 7;-2 1
| :
| | specs 77;-10 1
| :
Leslie
On 2022-06-22 07:45:43 Jeff Hennick wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I am in the process of adding FIELDS (and an enhanced FS/WS) to SPECS.
Currently having problems remembering how to get the stage to work in my
testing. Mike, I am using, and expanding, your idea/suggestion on changing
the spaces to something else that is not already in the record, etc. Thank
you! Jeff Hennick
</pre>
</blockquote>
</blockquote>
</body>
</html>
|
