Menu
▾
▴
netrexx-pipelines
You can subscribe to this list here.
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020 |
Jan
|
Feb
|
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(7) |
Jul
(10) |
Aug
(9) |
Sep
(9) |
Oct
(1) |
Nov
(3) |
Dec
(5) |
| 2021 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(3) |
Oct
(9) |
Nov
(1) |
Dec
(14) |
| 2022 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(165) |
Jul
(8) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(5) |
| 2023 |
Jan
(19) |
Feb
(14) |
Mar
(2) |
Apr
(3) |
May
|
Jun
(2) |
Jul
(10) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
(10) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: René J. <rvj...@xs...> - 2020-03-28 19:44:30
|
HI Jeff, great work! You do know that specs_test8.njp does not build? Thank you for adding all these things to specs! René. |
|
From: Colin K <CK-...@im...> - 2020-03-28 19:12:13
|
Hello all.
As I continue my little education into the world of creating filters
under NetRexx I have some more questions :-)
I notice that a number of the filters contain the statement:
exit(rc*(rc \= 12))
as the last line in the program. Where does the value 12 come from and
what does it represent? It seems to be a fairly common convention. The
only thing I can think of is that is a return that signifies that there
is no more data in the pipe and that the filter should shut down ??
Is there a list of return codes and their meaning anywhere?
I also notice that some filters, when reporting an error, use Emsg. For
example
Emsg(11,'Error - Input not a rexx object')
Is Emsg specially supposed to be only used in catch statements? Is Emsg
supposed to be used for any error message that is issued in the run method?
If I catch an error should one use Emsg or output(‘. . .error msg. . .’)
or just “say”. I presume ‘say’s get written directly to the console as
opposed to the primary output stream (which could be the console I
guess). Fair statement?
Thanks
Colin
|
|
From: <rvj...@xs...> - 2019-12-13 22:58:55
|
Just to mention that this problem has been resolved, and the pipes compiler works as designed again, so it it safe to build 3.09 from source. Many thanks to the designers and implementors of git bisect, which did exactly what it was intended to do, a binary search for the commit that caused the problem. René. > On 10 Dec 2019, at 18:03, René Jansen <rvj...@xs...> wrote: > > A small heads-up for those who build 3.09-PRE from source, please know that the pipes compiler is currently subtly broken: it compiles only one pipe from a series of pipes in a source file (leaving the rest as .nrx source files (which are OK to compile with nrc and reach the eventual goal). Also, .njp sources that contain a pipe specification and a stage definition in the same file (like addpipe(n).njp) are currently broken. I am aware of the problem (first looked for the solution in the wrong place, and thought it had to do with the new native executable) and will fix before the release of 3.09 GA. > > best regards, > > René. > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
|
From: René J. <rvj...@xs...> - 2019-12-10 22:03:28
|
A small heads-up for those who build 3.09-PRE from source, please know that the pipes compiler is currently subtly broken: it compiles only one pipe from a series of pipes in a source file (leaving the rest as .nrx source files (which are OK to compile with nrc and reach the eventual goal). Also, .njp sources that contain a pipe specification and a stage definition in the same file (like addpipe(n).njp) are currently broken. I am aware of the problem (first looked for the solution in the wrong place, and thought it had to do with the new native executable) and will fix before the release of 3.09 GA. best regards, René. |
|
From: René J. <rvj...@xs...> - 2019-11-03 19:20:08
|
Hi Jeff, I liked your idea for abbreviating the stage names to the sizes that CMS allows, as I saw in the abbrev.nrx stage, by inheriting the shortest name by the longer class names. I did this as a test for ‘console’ now. For some reason a public class needs its own program file name in NetRexx. I am not sure what the reason is for that, and we might considering changing that. We might try to use the compiler for allowable abbreviations, but the idea of a class per stage seems cleaner. I did fix some strictcase and strictargs issues in abbrev.nrx, but did not touch the inheritance problem yet. I wondered if there is a list somewhere - I looked into the ‘user guide and reference, and it seems that these minimal abbreviations are indicated by capitalization. I did not find a compact list anywhere, nor an ‘official’ explanation on how this works. If someone knows where to find it, please tell me (otherwise I’ll ask on the CMS Pipelines list). best regards, René. |
|
From: René J. <rvj...@xs...> - 2019-10-31 09:00:45
|
Hi Colin, this: http://vm.marist.edu/~pipeline/ <http://vm.marist.edu/~pipeline/> has a large collection of CMS Pipeline related information. IBM also has the manual online, the most recent one is: https://www.vm.ibm.com/library/710pdfs/71625200.pdf <https://www.vm.ibm.com/library/710pdfs/71625200.pdf> best regards, René. > On 31 Oct 2019, at 03:45, Colin <net...@im...> wrote: > > Hello > > Does anyone have a link or links to the latest and greatest CMS Pipeline Reference/Programming manual(s) that would be useful for learning about pipes? It has been a couple of decades since I have been involved with the mainframe (and even then it was MVS and VTAM related (although NetView did have REXX support)). > > Thanks > Colin > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
|
From: Colin <net...@im...> - 2019-10-31 02:59:25
|
Hello Does anyone have a link or links to the latest and greatest CMS Pipeline Reference/Programming manual(s) that would be useful for learning about pipes? It has been a couple of decades since I have been involved with the mainframe (and even then it was MVS and VTAM related (although NetView did have REXX support)). Thanks Colin |
|
From: Jeff H. <Je...@Je...> - 2019-10-30 23:45:06
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I have written what I hope are a comprehensive set of tests for
some of the existing stages. In doing so, I have found some
errors/omissions in some of the existing stages.</p>
<p>As a result, I have published tests for the BETWEEN and COMPARE
stages, and also published updated versions of those two.</p>
<p>These are in the SourceForge Code base now. Full
"railroad"-diagrams of the options are in both the stage and test
source files.<br>
</p>
<ul>
<li>BETWEEN</li>
<ul>
<li>Added CASELESS option to come up to the current CMS version</li>
<li>Fixed CASEANY, CASEIGNORE, and IGNORECASE logic to work with
the latest NetRexx</li>
</ul>
<li>COMPARE</li>
<ul>
<li>Note: This is not a stage in CMS, but it is very useful in
testing stages against expected output<br>
</li>
<li>Fixed for the first stream being shorter than the second</li>
<li>Fixed PAD Xorc handling</li>
<li>Added that control characters when in the report are
displayed as "blob"-characters</li>
<li>Fixed so two null streams are considered to be equal</li>
</ul>
<li>between_tests.njp</li>
<ul>
<li>11 tests<br>
</li>
</ul>
<li>compare_tests1.njp</li>
<ul>
<li>10 tests</li>
</ul>
<li>compare_tests2.njp</li>
<ul>
<li>10 tests</li>
</ul>
</ul>
<p>I will be adding more test sets and updated stages soon., and
announcing them here.<br>
</p>
<p>Jeff Hennick<br>
</p>
</body>
</html>
|
|
From: René J. <rvj...@xs...> - 2019-10-30 17:18:31
|
Welcome to the Pipelines for NetRexx mailing list! Its purpose is discussing development and use for Pipelines for NetRexx feature. As Pipelines users are accustomed to developing their own stages, these subjects are closely related; more closely, for example, than using the NetRexx translator and developing it. So in short, every contribution is welcome, be it signalling incompatibilities with CMS Pipelines, contribution of new stages, and discussion of the development of the pipelines compiler and its stages, or its integration and use of the NetRexx translator. René. |
