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: Colin <net...@im...> - 2021-10-31 05:52:42
|
Thanks Rene I am still a little confused though. I have a file called testpipe.nrx which has been copied from the Pipelines Quick Start manual z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin>dir testpipe* Volume in drive Z is OS Volume Serial Number is 643B-12E5 Directory of z:\NetRexx-4.01-GA\bin 2021-10-28 05:23 PM 334 testpipe.nrx 1 File(s) 334 bytes 0 Dir(s) 1,038,705,549,312 bytes free z:\NetRexx-4.01-GA\bin>type testpipe.nrx class testpipe method testpipe(avar=Rexx) F = Rexx 'abase' T = Rexx 1 F[0]=5 F[1]=222 F[2]=3333 F[3]=1111 F[4]=55 F[5]=444 pipe (apipe stall 1000 ) stem F | sort | prefix literal {avar} | console | stem T loop i=1 to T[0] say 'T['i']='T[i] end method main(a=String[]) static testpipe(Rexx(a)) z:\NetRexx-4.01-GA\bin> My understanding is that I am supposed to use pipc to compile it. z:\NetRexx-4.01-GA\bin>pipc testpipe 16 +++ stem F | sort | prefix literal {avar} | console | stem T +++ ^ +++ Error: Unexpected character found in source: '{' (hexadecimal encoding: 007B) z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin>dir testpipe* Volume in drive Z is OS Volume Serial Number is 643B-12E5 Directory of z:\NetRexx-4.01-GA\bin 2021-10-28 05:23 PM 334 testpipe.nrx 1 File(s) 334 bytes 0 Dir(s) 1,038,709,510,144 bytes free Hmmm.. . . maybe I am supposed to call it testpipe.njp. Let's rename it. z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin>rename testpipe.nrx testpipe.njp z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin>dir testpipe* Volume in drive Z is OS Volume Serial Number is 643B-12E5 Directory of z:\NetRexx-4.01-GA\bin 2021-10-28 05:23 PM 334 testpipe.njp 1 File(s) 334 bytes 0 Dir(s) 1,038,709,354,496 bytes free z:\NetRexx-4.01-GA\bin>pipc testpipe pipe (testpipe_apipe stall 1000 ) stem F | sort | prefix literal arg(string 'avar'} | console | stem T z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin>dir testpipe* Volume in drive Z is OS Volume Serial Number is 643B-12E5 Directory of z:\NetRexx-4.01-GA\bin 2021-10-30 10:31 PM 1,845 testpipe.class 2021-10-28 05:23 PM 334 testpipe.njp 2021-10-30 10:31 PM 4,180 testpipe_apipe.class 2021-10-30 10:31 PM 314 testpipe_apipe_sortRexx_2.class 4 File(s) 6,673 bytes 0 Dir(s) 1,038,709,751,808 bytes free This looks much more promising. Let's run it. z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin> z:\NetRexx-4.01-GA\bin>java testpipe Error: Unable to initialize main class testpipe Caused by: java.lang.NoClassDefFoundError: org/netrexx/njpipes/pipes/ThreadQ That didn't work so I wonder if I am supposed to execute the testpipe_apipe.class instead. z:\NetRexx-4.01-GA\bin>java testpipe_apipe.class Error: Could not find or load main class testpipe_apipe.class Caused by: java.lang.ClassNotFoundException: testpipe_apipe.class z:\NetRexx-4.01-GA\bin> Not sure what I am doing wrong. Thanks Colin On 2021-10-30 07:23, René Jansen wrote: > Hi Leslie, Colin, > > This source needs the pipes compiler - please try with pipc (pipc: aliased to java org.netrexx.njpipes.pipes.compiler) - it needs that step to sort out the variable inclusion. Colins analysis that the NetRexx compiler cannot handle this is correct. If you can include a version of the source that does not include | (pipes) at the start I can easier check that for you. > > Best regards, > > René. > > >> On 28 Oct 2021, at 12:36, J Leslie Turriff<jlt...@ma...> wrote: >> >> I'm trying to use a simple pipeline in a NetRexx routine, but nrc doesn't like my >> variable substitution: >> >> ~/bin/NetRexx >> | $ echo $JAVA_HOME >> | >> | @05:27:11,leslie@pinto rc=0 >> | ~/bin/NetRexx >> | $ echo $CLASSPATH >> | .:/home/leslie/bin/NetRexx/:/usr/java/jdk-17:/usr/local/NetRexx-4.01-GA/lib/NetRexxF.jar >> | @05:27:21,leslie@pinto rc=0 >> | ~/bin/NetRexx >> | $ cat newTree.nrx >> | -- .-----------------------------------------------------------------------. -- >> | -- | Change Log | -- >> | -- |Version Date Description | -- >> | -- |------- ---------- ----------------------------------------------------| -- >> | -- | | -- >> | -- |1.0 2021-10-27 Creation | -- >> | -- '-----------------------------------------------------------------------' -- >> | import org.netrexx.njpipes.pipes. >> | trace off >> | parse arg treeBase >> | treePipe(Rexx(treeBase)) >> | exit 0 >> | ------------------------------------------------------------------------------- >> | method treePipe(treeArguments) >> | pipe (fixTree) >> | command /usr/bin/tree {treeArguments} >> | | tree: split at /[/ >> | | merge: specs select 1 1-* next >> | select 0 1-* next >> | select 2 1-* next >> | | console >> | ? tree: split at /]/ | attrs: >> | ? attrs: | merge: >> | --===========================================================================-- >> | @05:27:31,leslie@pinto rc=0 >> | ~/bin/NetRexx >> | $ nrc newTree.nrx >> | NetRexx portable processor 4.01-GA build 573-20210320-2000 >> | Copyright (c) RexxLA, 2011,2021. All rights reserved. >> | Parts Copyright (c) IBM Corporation, 1995,2008. >> | Program newTree.nrx >> | 16 +++ command /usr/bin/tree {treeArguments} >> | +++ ^ >> | +++ Error: Unexpected character found in source: '{' (hexadecimal encoding: 007B) >> | Compilation of 'newTree.nrx' failed [one error] >> | @05:27:40,leslie@pinto rc=2 >> >> I can't see what I'm doing differently to what is described in "How to use a pipe in a >> NetRexx program", page 24 of "Pipelines Guide and Reference"; I tried first putting the >> pipeline into the implicit main() method, then in a separate method; neither worked, so I >> looked through the examples in the NetRexx package and noticed the import statement, but >> adding that didn't help either. >> What am I doing wrong? >> >> Leslie >> -- >> Distribution: openSUSE Leap 15.3 x86_64 >> java version "17" 2021-09-14 LTS >> Java(TM) SE Runtime Environment (build 17+35-LTS-2724) >> Java HotSpot(TM) 64-Bit Server VM (build 17+35-LTS-2724, mixed mode, sharing) >> NetRexx portable processor 4.01-GA build 573-20210320-2000 >> >> >> _______________________________________________ >> netrexx-pipelines mailing list >> net...@li... >> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: René J. <rvj...@xs...> - 2021-10-30 14:28:19
|
Hi Leslie, Colin, This source needs the pipes compiler - please try with pipc (pipc: aliased to java org.netrexx.njpipes.pipes.compiler) - it needs that step to sort out the variable inclusion. Colins analysis that the NetRexx compiler cannot handle this is correct. If you can include a version of the source that does not include | (pipes) at the start I can easier check that for you. Best regards, René. > On 28 Oct 2021, at 12:36, J Leslie Turriff <jlt...@ma...> wrote: > > I'm trying to use a simple pipeline in a NetRexx routine, but nrc doesn't like my > variable substitution: > > ~/bin/NetRexx > | $ echo $JAVA_HOME > | > | @05:27:11,leslie@pinto rc=0 > | ~/bin/NetRexx > | $ echo $CLASSPATH > | .:/home/leslie/bin/NetRexx/:/usr/java/jdk-17:/usr/local/NetRexx-4.01-GA/lib/NetRexxF.jar > | @05:27:21,leslie@pinto rc=0 > | ~/bin/NetRexx > | $ cat newTree.nrx > | -- .-----------------------------------------------------------------------. -- > | -- | Change Log | -- > | -- |Version Date Description | -- > | -- |------- ---------- ----------------------------------------------------| -- > | -- | | -- > | -- |1.0 2021-10-27 Creation | -- > | -- '-----------------------------------------------------------------------' -- > | import org.netrexx.njpipes.pipes. > | trace off > | parse arg treeBase > | treePipe(Rexx(treeBase)) > | exit 0 > | ------------------------------------------------------------------------------- > | method treePipe(treeArguments) > | pipe (fixTree) > | command /usr/bin/tree {treeArguments} > | | tree: split at /[/ > | | merge: specs select 1 1-* next > | select 0 1-* next > | select 2 1-* next > | | console > | ? tree: split at /]/ | attrs: > | ? attrs: | merge: > | --===========================================================================-- > | @05:27:31,leslie@pinto rc=0 > | ~/bin/NetRexx > | $ nrc newTree.nrx > | NetRexx portable processor 4.01-GA build 573-20210320-2000 > | Copyright (c) RexxLA, 2011,2021. All rights reserved. > | Parts Copyright (c) IBM Corporation, 1995,2008. > | Program newTree.nrx > | 16 +++ command /usr/bin/tree {treeArguments} > | +++ ^ > | +++ Error: Unexpected character found in source: '{' (hexadecimal encoding: 007B) > | Compilation of 'newTree.nrx' failed [one error] > | @05:27:40,leslie@pinto rc=2 > > I can't see what I'm doing differently to what is described in "How to use a pipe in a > NetRexx program", page 24 of "Pipelines Guide and Reference"; I tried first putting the > pipeline into the implicit main() method, then in a separate method; neither worked, so I > looked through the examples in the NetRexx package and noticed the import statement, but > adding that didn't help either. > What am I doing wrong? > > Leslie > -- > Distribution: openSUSE Leap 15.3 x86_64 > java version "17" 2021-09-14 LTS > Java(TM) SE Runtime Environment (build 17+35-LTS-2724) > Java HotSpot(TM) 64-Bit Server VM (build 17+35-LTS-2724, mixed mode, sharing) > NetRexx portable processor 4.01-GA build 573-20210320-2000 > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: ColinK <ibm...@im...> - 2021-10-30 04:01:14
|
Hi Leslie. While I am not very knowledgeable about the NetRexx compiler and its inner workings I was curious about this and decided to have a peek ( or peekto() in pipe lingo :-) ) I copied the testpipe code found in the "How to use a pipe in a NetRexx program" and got the same error as you received. It looks to me like the error message is being generated in RxClauser.nrx. In browsing the source one see the following . . . /* Here is the setup table for 'standard' NetRexx characters. */ /* Note: white space is handled before translation, for speed. */ /* This table handles the 'core' characters. Unicode letters and */ /* digits (>'\x7f') are handled in-line, when encountered. */ /* White space characters are also in the table. */ /* Note: the euro character (\u20ac) is not in the table as it */ /* would cause the table to become 8K long; it's special-cased. */ intrans=char[]- ('abcdefghijklmnopqrstuvwxyz'- ||'ABCDEFGHIJKLMNOPQRSTUVWXYZ'- ||'_$'- -- special symbol characters ||'1234567890'- ||'+-/*\\%&|=<>@'- -- '\\' here is '\' ||'.()[]"'';,'- ||'\t\f') outrans=char[]- ('ssssssssssssssssssssssssss'- -- 's' is non-digit symbol ||'ssssssssssssssssssssssssss'- ||'ss'- ||'nnnnnnnnnn'- -- 'n' is digit ||'oooooooooooo'- -- 'o' is operator ||'.()[]"'';,'- -- specials are themselves ||' ') -- whitespace . . . Note that the curly brace is not represented which. . . select when cchar=' ' then /* blank */ do -- special-case, for speed hadblank=pos; pos=pos+1; iterate; end when cchar<=tranmax then ctype=trantable[int(cchar)] when Character.isJavaIdentifierStart(cchar) then ctype='s' -- symbol start NETREXX-6 rvj 20130710 -- when cchar='\u20ac' then ctype='s' -- the euro (is a true JavaIdentifierStart now) when Character.isDigit(cchar) & - -- number start? Character.digit(cchar, 10)>=0 then ctype='n' -- base 10? otherwise *ctype=BAD* end . . . I think results in ctype being set to BAD. . . . . .and thus resulting in the error message you received. if *ctype=BAD* then do if rxt.program.flag.diag then do say '# BAD char ctype: '''ctype''''- Character.isLetter(cchar) Character.isDigit(cchar)- Character.isLetterOrDigit(cchar) Character.isDefined(cchar) - Character.isJavaIdentifierStart(cchar) Character.isJavaIdentifierPart(cchar) end *signal RxQuit(rxt, tok, 'invalid.character', cchar,-** ** Rexx(int(cchar)).d2x(4))* end Since it looks like the only piece of NetRexx that uses the curly braces is related to the pipes stuff one might suppose that there must be support for pipes built into the compiler and so we should find some pipe references somewhere in the compiler programs. Apparently not. . . CK@DESKTOP-C91GVBB MINGW64 ~/NetRexx/v401/src/org/netrexx/process (master) $ grep -i pipe * NrVersion.nrx: pipesversion = 'Pipelines for NetRexx version 'version NrVersion.nrx: pipescopyright = 'Copyright (c) E. J. Tomlinson, 1999-2011. All rights reserved.\nParts Copyright (c) RexxLA, 2011-2021. All rights reserved.' NrVersion.nrx: method getPipesVersion() NrVersion.nrx: return this.pipesversion NrVersion.nrx: method getPipesCopyright() NrVersion.nrx: return this.pipescopyright CK@DESKTOP-C91GVBB MINGW64 ~/NetRexx/v401/src/org/netrexx/process (master) $ cd ~/NetRexx/v308/src/org/netrexx/process CK@DESKTOP-C91GVBB MINGW64 ~/NetRexx/v308/src/org/netrexx/process (master) $ grep -i pipe * NrVersion.nrx: pipesversion = 'Pipelines for NetRexx version 'version NrVersion.nrx: pipescopyright = 'Copyright (c) E. J. Tomlinson, 1999-2011. All rights reserved.\nParts Copyright (c) RexxLA, 2011-2020. All rights reserved.' NrVersion.nrx: method getPipesVersion() NrVersion.nrx: return this.pipesversion NrVersion.nrx: method getPipesCopyright() NrVersion.nrx: return this.pipescopyright CK@DESKTOP-C91GVBB MINGW64 ~/NetRexx/v308/src/org/netrexx/process (master) $ I am going to have to leave this interesting conumdrum to the NetRexx experts that know how the compiler works to comment further. I am probably way off base anyhow ( more than likely I am not looking in the place :-) ) Sorry I couldn't be of much help on this one. Cheers Colin K [PS. Should this be sent to the groups.io NetRexx list?? ] On 2021-10-28 03:36, J Leslie Turriff wrote: > I'm trying to use a simple pipeline in a NetRexx routine, but nrc doesn't like my > variable substitution: > > ~/bin/NetRexx > | $ echo $JAVA_HOME > | > | @05:27:11,leslie@pinto rc=0 > | ~/bin/NetRexx > | $ echo $CLASSPATH > | .:/home/leslie/bin/NetRexx/:/usr/java/jdk-17:/usr/local/NetRexx-4.01-GA/lib/NetRexxF.jar > | @05:27:21,leslie@pinto rc=0 > | ~/bin/NetRexx > | $ cat newTree.nrx > | -- .-----------------------------------------------------------------------. -- > | -- | Change Log | -- > | -- |Version Date Description | -- > | -- |------- ---------- ----------------------------------------------------| -- > | -- | | -- > | -- |1.0 2021-10-27 Creation | -- > | -- '-----------------------------------------------------------------------' -- > | import org.netrexx.njpipes.pipes. > | trace off > | parse arg treeBase > | treePipe(Rexx(treeBase)) > | exit 0 > | ------------------------------------------------------------------------------- > | method treePipe(treeArguments) > | pipe (fixTree) > | command /usr/bin/tree {treeArguments} > | | tree: split at /[/ > | | merge: specs select 1 1-* next > | select 0 1-* next > | select 2 1-* next > | | console > | ? tree: split at /]/ | attrs: > | ? attrs: | merge: > | --===========================================================================-- > | @05:27:31,leslie@pinto rc=0 > | ~/bin/NetRexx > | $ nrc newTree.nrx > | NetRexx portable processor 4.01-GA build 573-20210320-2000 > | Copyright (c) RexxLA, 2011,2021. All rights reserved. > | Parts Copyright (c) IBM Corporation, 1995,2008. > | Program newTree.nrx > | 16 +++ command /usr/bin/tree {treeArguments} > | +++ ^ > | +++ Error: Unexpected character found in source: '{' (hexadecimal encoding: 007B) > | Compilation of 'newTree.nrx' failed [one error] > | @05:27:40,leslie@pinto rc=2 > > I can't see what I'm doing differently to what is described in "How to use a pipe in a > NetRexx program", page 24 of "Pipelines Guide and Reference"; I tried first putting the > pipeline into the implicit main() method, then in a separate method; neither worked, so I > looked through the examples in the NetRexx package and noticed the import statement, but > adding that didn't help either. > What am I doing wrong? > > Leslie > -- > Distribution: openSUSE Leap 15.3 x86_64 > java version "17" 2021-09-14 LTS > Java(TM) SE Runtime Environment (build 17+35-LTS-2724) > Java HotSpot(TM) 64-Bit Server VM (build 17+35-LTS-2724, mixed mode, sharing) > NetRexx portable processor 4.01-GA build 573-20210320-2000 > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: J L. T. <jlt...@ma...> - 2021-10-28 10:53:15
|
I'm trying to use a simple pipeline in a NetRexx routine, but nrc doesn't like my variable substitution: ~/bin/NetRexx | $ echo $JAVA_HOME | | @05:27:11,leslie@pinto rc=0 | ~/bin/NetRexx | $ echo $CLASSPATH | .:/home/leslie/bin/NetRexx/:/usr/java/jdk-17:/usr/local/NetRexx-4.01-GA/lib/NetRexxF.jar | @05:27:21,leslie@pinto rc=0 | ~/bin/NetRexx | $ cat newTree.nrx | -- .-----------------------------------------------------------------------. -- | -- | Change Log | -- | -- |Version Date Description | -- | -- |------- ---------- ----------------------------------------------------| -- | -- | | -- | -- |1.0 2021-10-27 Creation | -- | -- '-----------------------------------------------------------------------' -- | import org.netrexx.njpipes.pipes. | trace off | parse arg treeBase | treePipe(Rexx(treeBase)) | exit 0 | ------------------------------------------------------------------------------- | method treePipe(treeArguments) | pipe (fixTree) | command /usr/bin/tree {treeArguments} | | tree: split at /[/ | | merge: specs select 1 1-* next | select 0 1-* next | select 2 1-* next | | console | ? tree: split at /]/ | attrs: | ? attrs: | merge: | --===========================================================================-- | @05:27:31,leslie@pinto rc=0 | ~/bin/NetRexx | $ nrc newTree.nrx | NetRexx portable processor 4.01-GA build 573-20210320-2000 | Copyright (c) RexxLA, 2011,2021. All rights reserved. | Parts Copyright (c) IBM Corporation, 1995,2008. | Program newTree.nrx | 16 +++ command /usr/bin/tree {treeArguments} | +++ ^ | +++ Error: Unexpected character found in source: '{' (hexadecimal encoding: 007B) | Compilation of 'newTree.nrx' failed [one error] | @05:27:40,leslie@pinto rc=2 I can't see what I'm doing differently to what is described in "How to use a pipe in a NetRexx program", page 24 of "Pipelines Guide and Reference"; I tried first putting the pipeline into the implicit main() method, then in a separate method; neither worked, so I looked through the examples in the NetRexx package and noticed the import statement, but adding that didn't help either. What am I doing wrong? Leslie -- Distribution: openSUSE Leap 15.3 x86_64 java version "17" 2021-09-14 LTS Java(TM) SE Runtime Environment (build 17+35-LTS-2724) Java HotSpot(TM) 64-Bit Server VM (build 17+35-LTS-2724, mixed mode, sharing) NetRexx portable processor 4.01-GA build 573-20210320-2000 |
From: René J. <rvj...@xs...> - 2021-10-12 13:41:43
|
Hi Leslie Yes, they are - the intention was that the current version of NetRexx was indicated in the example, but then, I should not have told the formatter that the text was literal code. I’ll correct that for 4.02! Best regards, René. > On 6 Oct 2021, at 06:29, J Leslie Turriff <jlt...@ma...> wrote: > > I came across these odd-looking examples on pp 96, 97 of the NetRexx Language Reference, > Version 4.01-GA of March 20, 2021: > > | Example: > | > | parse wordlist word1 wordlist > | > | In this idiomatic example, the first word is removed from wordlist and is as- > | signed to the variable word1, and the remainder is assigned back to wordlist. > | > | Notes: > | > | 1. The special words ask, source, and version, as described in the section Spe- > | cial names and methods(see page 121), allow: > | > | parse ask x -- parses a line from input stream > | parse source x -- parses 'Java method \emph{filename}' > | > | 96 > | > | parse version x -- parses '\nr{} \emph{version} \emph{date}' > | These special words may also be used within expressions. > | > | 2. Similarly, it is recommended that the initial (main) method in a stand-alone > | application place the command string passed to it in a variable called arg. > | 53 > | If this is done, the instruction: > | > | parse arg template > | > | will work, in a stand-alone application, in the same way as in REXX (even > | though arg is not a keyword in this case). 54 > > Are the strings "\nr{}" and "\emph{...}" formatting errors? > > Leslie > > Distribution: openSUSE Leap 15.3 x86_64 > NetRexx: NetRexx 4.01-GA > -- > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: J L. T. <jlt...@ma...> - 2021-10-06 04:29:59
|
I came across these odd-looking examples on pp 96, 97 of the NetRexx Language Reference, Version 4.01-GA of March 20, 2021: | Example: | | parse wordlist word1 wordlist | | In this idiomatic example, the first word is removed from wordlist and is as- | signed to the variable word1, and the remainder is assigned back to wordlist. | | Notes: | | 1. The special words ask, source, and version, as described in the section Spe- | cial names and methods(see page 121), allow: | | parse ask x -- parses a line from input stream | parse source x -- parses 'Java method \emph{filename}' | | 96 | | parse version x -- parses '\nr{} \emph{version} \emph{date}' | These special words may also be used within expressions. | | 2. Similarly, it is recommended that the initial (main) method in a stand-alone | application place the command string passed to it in a variable called arg. | 53 | If this is done, the instruction: | | parse arg template | | will work, in a stand-alone application, in the same way as in REXX (even | though arg is not a keyword in this case). 54 Are the strings "\nr{}" and "\emph{...}" formatting errors? Leslie Distribution: openSUSE Leap 15.3 x86_64 NetRexx: NetRexx 4.01-GA -- |
From: René J. <rvj...@xs...> - 2021-09-14 15:49:33
|
Good idea, but I think that gets complicated quickly - we have z/OS, z/OS USS (EBCDIC), WAS on Z (Unicode), but also Linux on Z (Unicode). And which EBCDIC codepage? We would need JZOS to figure that out, and then still. But I am going to investigate it. René. > On 14 Sep 2021, at 16:27, J Leslie Turriff <jlt...@ma...> wrote: > > Can NetRexx pipe not query the platform, and if it is zSeries, emit EBCDIC, or if not, > Unicode? > > Leslie > >> On 2021-09-13 16:51:44 René Jansen wrote: >> Hi Jeff, >> >> this was left untouched for longer than I wanted. Current state is, DIGEST >> does what I needed it for and can do different cryptohashes with >> demonstrable correctness when e.g. comparing to the wikipedia reference >> examples: >> >> ➜ netrexx-code git:(master) ✗ pipe "literal The quick brown fox jumps over >> the lazy dog | digest md5 | cons" 9e107d9d372bb6826bd81d3542a419d6 >> ➜ netrexx-code git:(master) ✗ pipe "literal The quick brown fox jumps over >> the lazy dog. | digest md5 | cons" e4d909c290d0fb1ca068ffaddf22cbd0 >> >> But: CMS returns characters and we return a hex string. Problem is that the >> characters on CMS are always EBCDIC and we do Unicode. For compatibility, >> are we expected to output EBCDIC on all platforms? Also, the trailing space >> is tricky on CMS, we have no real answer to that at the moment but it has >> never bitten. >> >> Things being as they are - like the amount of time I can invest - I am >> inclined to just document the difference and leaving it like this. I am >> convinced most people want a hex string anyway, because that is how digests >> are used. >> >> p.s. I did a small change to the SQLSELECT stage - if it is DB2, you can’t >> override set properties with the url. Also, the name of the jdbc driver was >> seriously out of date. >> >> best regards, >> >> René. >> >> _______________________________________________ >> netrexx-pipelines mailing list >> net...@li... >> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines > > > Distribution: openSUSE Leap 15.3 x86_64 > > -- > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: J L. T. <jlt...@ma...> - 2021-09-14 14:27:52
|
Can NetRexx pipe not query the platform, and if it is zSeries, emit EBCDIC, or if not, Unicode? Leslie On 2021-09-13 16:51:44 René Jansen wrote: > Hi Jeff, > > this was left untouched for longer than I wanted. Current state is, DIGEST > does what I needed it for and can do different cryptohashes with > demonstrable correctness when e.g. comparing to the wikipedia reference > examples: > > ➜ netrexx-code git:(master) ✗ pipe "literal The quick brown fox jumps over > the lazy dog | digest md5 | cons" 9e107d9d372bb6826bd81d3542a419d6 > ➜ netrexx-code git:(master) ✗ pipe "literal The quick brown fox jumps over > the lazy dog. | digest md5 | cons" e4d909c290d0fb1ca068ffaddf22cbd0 > > But: CMS returns characters and we return a hex string. Problem is that the > characters on CMS are always EBCDIC and we do Unicode. For compatibility, > are we expected to output EBCDIC on all platforms? Also, the trailing space > is tricky on CMS, we have no real answer to that at the moment but it has > never bitten. > > Things being as they are - like the amount of time I can invest - I am > inclined to just document the difference and leaving it like this. I am > convinced most people want a hex string anyway, because that is how digests > are used. > > p.s. I did a small change to the SQLSELECT stage - if it is DB2, you can’t > override set properties with the url. Also, the name of the jdbc driver was > seriously out of date. > > best regards, > > René. > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines Distribution: openSUSE Leap 15.3 x86_64 -- |
From: René J. <rvj...@xs...> - 2021-09-13 21:52:09
|
Hi Jeff, this was left untouched for longer than I wanted. Current state is, DIGEST does what I needed it for and can do different cryptohashes with demonstrable correctness when e.g. comparing to the wikipedia reference examples: ➜ netrexx-code git:(master) ✗ pipe "literal The quick brown fox jumps over the lazy dog | digest md5 | cons" 9e107d9d372bb6826bd81d3542a419d6 ➜ netrexx-code git:(master) ✗ pipe "literal The quick brown fox jumps over the lazy dog. | digest md5 | cons" e4d909c290d0fb1ca068ffaddf22cbd0 But: CMS returns characters and we return a hex string. Problem is that the characters on CMS are always EBCDIC and we do Unicode. For compatibility, are we expected to output EBCDIC on all platforms? Also, the trailing space is tricky on CMS, we have no real answer to that at the moment but it has never bitten. Things being as they are - like the amount of time I can invest - I am inclined to just document the difference and leaving it like this. I am convinced most people want a hex string anyway, because that is how digests are used. p.s. I did a small change to the SQLSELECT stage - if it is DB2, you can’t override set properties with the url. Also, the name of the jdbc driver was seriously out of date. best regards, René. |
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> |
From: René J. <rvj...@xs...> - 2021-08-19 10:10:16
|
[changed subject line and crossposted] 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! Best regards, René. > On 19 Aug 2021, at 12:04, m-stgt <m-...@us...> wrote: > > Ok, little subject drift -- Gil Barmwater and Erich, hello! > 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 "the Book" <http://vm.marist.edu/%7Epipeline/pipeline.pdf> 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. > 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. > > How may offspring tell parent to do something? <https://sourceforge.net/p/oorexx/discussion/408478/thread/a794679bb8/?limit=25#bf23/1a7b/43be/640c/a0b0> > Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/oorexx/discussion/408478/ <https://sourceforge.net/p/oorexx/discussion/408478/> > To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ <https://sourceforge.net/auth/subscriptions/> |
From: Jeff H. <Je...@Je...> - 2021-08-18 19:25:29
|
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <pre class="moz-quote-pre" wrap=""><font size="+1">René</font></pre> <p>Good to hear from you, and I hope you and yours are doing well. I am doing so, keeping busy with summer activities and friends.</p> <p>CMS' LITERAL syntax documentation says "Leading and trailing blanks are significant." I missed that when doing the NetRexx Pipelines stage testing and documentation. The NR Pipelines stage just passes the string via a NetRexx method argument, which strips off both leading and trailing blanks. I don't know how to get around that. So for now, the NR documentation for LITERAL should note this difference and offer the workaround of STRLITERAL. If LITERAL could be fixed so the string extends with blanks to the stage-separator, I expect many current pipes that are formatted vertically (and some horizontally) would suddenly work differently. I have no good idea on which presents the lesser damage. I do suspect that there are very few (CMS) pipes with LITERAL stages that have significant trailing blanks. Probably more with leading blanks so the output text aligns.<br> </p> <p>In my opinion, DIGEST (as any existing stage) should work as in CMS. But many of our users in the PC/Java world will want the hex output. The two stage solution works, but could we add a HEX option with BYTES the default? Or would it be better to have a new stage: DIGESTHEX?</p> <font face="monospace"> <font color="red">+--BYTES--+</font></font><br> <font face="monospace"> >>--DIGEST--+--SHA1----+--<font color="red">+---------+</font>--+----------------+-->></font><br> <font face="monospace"> +--SHA256--+ <font color="red">+--HEX----+</font> +--APPEND--------+</font><br> <font face="monospace"> + etc. + + +<br> </font> <p>As for the symposium, I have no ideas on what to say, but would be honored to be able to present.</p> <p>Jeff<br> </p> <div class="moz-cite-prefix">On 8/18/2021 9:41 AM, René Jansen wrote:<br> </div> <blockquote type="cite" cite="mid:5B1...@xs..."> <pre class="moz-quote-pre" wrap="">Hi Jeff, How are you? Just found out about a corner case in Pipelines for NetRexx - I was implementing DIGEST and in an effort to be CMS compatible I noticed that the hash is not returned in hex on CMS, but as bytes, which you can later translate. Not being able to get the same hashes, I noticed that I needed an XLATE E2A before the DIGEST stage, and then still it would not work. So dumping every stage with SPECS 1-* C2X 1 I noticed that CMS Pipelines has an extra space in the pipeline, unless I put the pipe separator litterally at the end of the string. And lo and behold, in the source for the LITERAL stage it actually tells us (Ed does) that CMS does preserve trailing spaces, and njpipes does not. What do you think, do we need to fix this? And also, Do we want to have DIGEST output bytes instead of hex? I am leaning to ‘yes’ on both counts, but I would like to hear what you think, and whether fixing LITERAL will break anything. Other thing, do you think you can present at the symposium, when that is online and somewhere in October? Best regards. René. _______________________________________________ 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> |
From: René J. <rvj...@xs...> - 2021-08-18 13:41:14
|
Hi Jeff, How are you? Just found out about a corner case in Pipelines for NetRexx - I was implementing DIGEST and in an effort to be CMS compatible I noticed that the hash is not returned in hex on CMS, but as bytes, which you can later translate. Not being able to get the same hashes, I noticed that I needed an XLATE E2A before the DIGEST stage, and then still it would not work. So dumping every stage with SPECS 1-* C2X 1 I noticed that CMS Pipelines has an extra space in the pipeline, unless I put the pipe separator litterally at the end of the string. And lo and behold, in the source for the LITERAL stage it actually tells us (Ed does) that CMS does preserve trailing spaces, and njpipes does not. What do you think, do we need to fix this? And also, Do we want to have DIGEST output bytes instead of hex? I am leaning to ‘yes’ on both counts, but I would like to hear what you think, and whether fixing LITERAL will break anything. Other thing, do you think you can present at the symposium, when that is online and somewhere in October? Best regards. René. |
From: J L. T. <jlt...@ma...> - 2021-04-18 06:45:53
|
I can't find anything in the NetRexx documentation about upgrading. Do I just overlay the old directory tree with the new one, or is something else necessary? Leslie openSUSE Leap 15.2 x86_64 -- |
From: Jeff H. <Je...@Je...> - 2021-03-27 11:10:41
|
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p>Not that I have ever seen.</p> <p>Any artists on this list?</p> <p>Jeff<br> </p> <div class="moz-cite-prefix">On 3/27/2021 12:56 AM, J Leslie Turriff wrote:<br> </div> <blockquote type="cite" cite="mid:202...@ma..."> <pre class="moz-quote-pre" wrap=""> Various flavours of Rexx, including NetRexx, have icons that can be associated with their filetypes. Is there one for NetRexx Pipeline files? Leslie openSUSE Leap 15.2 x86_64 -- _______________________________________________ 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> |
From: J L. T. <jlt...@ma...> - 2021-03-27 04:56:31
|
Various flavours of Rexx, including NetRexx, have icons that can be associated with their filetypes. Is there one for NetRexx Pipeline files? Leslie openSUSE Leap 15.2 x86_64 -- |
From: Marc R. <re...@gm...> - 2021-03-16 10:10:16
|
Hi Leslie, Colin, this is fixed in 4.01, soon to be released. Marc On 3/12/21 6:29 AM, Colin wrote: > Hello Leslie > > I always thought that the first word after the ( is supposed to be the name of the generated class file but I see now > that it is 'not mandatory'. Looks like this may be a bug. > > z:\>java org.netrexx.njpipes.pipes.runner "pipe (end !) literal Works?|console" > 59 +++ _s_2 = () > +++ ^ > +++ Error: Expression expected > Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.rangeCheck(Unknown Source) > at java.util.ArrayList.get(Unknown Source) > at org.netrexx.process.NetRexxC.clgMain(NetRexxC.java:217) > at org.netrexx.njpipes.pipes.compiler.compile(compiler.java:1240) > at org.netrexx.njpipes.pipes.compiler.<init>(compiler.java:1337) > at org.netrexx.njpipes.pipes.runner.main(runner.java:76) > > z:\>java org.netrexx.njpipes.pipes.runner "pipe (*test1* end !) literal Works?|console" > Works? > > I don't have the latest versions installed yet but the issue exists in 3.08 as well and perhaps even in earlier versions. > > Cheers > Colin > > On 2021-03-11 18:00, J Leslie Turriff wrote: >> | $ pipe '(end !) literal Works?|console' >> | 59 +++ _s_2 = () >> | +++ ^ >> | +++ Error: Expression expected >> | Exception in thread "main" java.lang.IndexOutOfBoundsException: Index 0 out of bounds >> for length 0 >> | at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) >> | at >> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) >> | at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) >> | at java.base/java.util.Objects.checkIndex(Objects.java:372) >> | at java.base/java.util.ArrayList.get(ArrayList.java:459) >> | at org.netrexx.process.NetRexxC.clgMain(NetRexxC.java:217) >> | at org.netrexx.njpipes.pipes.compiler.compile(compiler.java:1260) >> | at org.netrexx.njpipes.pipes.compiler.<init>(compiler.java:1357) >> | at org.netrexx.njpipes.pipes.runner.main(runner.java:76) >> >> According to page 17 of the NetRexx Pipelines Quick Start Guide (Version 4.01-beta3 of >> December 25, 2020), this ought to work. What am I missing? >> >> Leslie >> >> openjdk version "11.0.10" 2021-01-19 >> OpenJDK Runtime Environment (build 11.0.10+9-suse-lp152.2.9.1-x8664) >> OpenJDK 64-Bit Server VM (build 11.0.10+9-suse-lp152.2.9.1-x8664, mixed mode) >> openSUSE Leap 15.2 x86_64 >> -- >> >> >> _______________________________________________ >> netrexx-pipelines mailing list >> net...@li... >> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines > > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines > |
From: Colin <net...@im...> - 2021-03-12 05:43:07
|
Hello Leslie I always thought that the first word after the ( is supposed to be the name of the generated class file but I see now that it is 'not mandatory'. Looks like this may be a bug. z:\>java org.netrexx.njpipes.pipes.runner "pipe (end !) literal Works?|console" 59 +++ _s_2 = () +++ ^ +++ Error: Expression expected Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(Unknown Source) at java.util.ArrayList.get(Unknown Source) at org.netrexx.process.NetRexxC.clgMain(NetRexxC.java:217) at org.netrexx.njpipes.pipes.compiler.compile(compiler.java:1240) at org.netrexx.njpipes.pipes.compiler.<init>(compiler.java:1337) at org.netrexx.njpipes.pipes.runner.main(runner.java:76) z:\>java org.netrexx.njpipes.pipes.runner "pipe (*test1* end !) literal Works?|console" Works? I don't have the latest versions installed yet but the issue exists in 3.08 as well and perhaps even in earlier versions. Cheers Colin On 2021-03-11 18:00, J Leslie Turriff wrote: > | $ pipe '(end !) literal Works?|console' > | 59 +++ _s_2 = () > | +++ ^ > | +++ Error: Expression expected > | Exception in thread "main" java.lang.IndexOutOfBoundsException: Index 0 out of bounds > for length 0 > | at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) > | at > java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) > | at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) > | at java.base/java.util.Objects.checkIndex(Objects.java:372) > | at java.base/java.util.ArrayList.get(ArrayList.java:459) > | at org.netrexx.process.NetRexxC.clgMain(NetRexxC.java:217) > | at org.netrexx.njpipes.pipes.compiler.compile(compiler.java:1260) > | at org.netrexx.njpipes.pipes.compiler.<init>(compiler.java:1357) > | at org.netrexx.njpipes.pipes.runner.main(runner.java:76) > > According to page 17 of the NetRexx Pipelines Quick Start Guide (Version 4.01-beta3 of > December 25, 2020), this ought to work. What am I missing? > > Leslie > > openjdk version "11.0.10" 2021-01-19 > OpenJDK Runtime Environment (build 11.0.10+9-suse-lp152.2.9.1-x8664) > OpenJDK 64-Bit Server VM (build 11.0.10+9-suse-lp152.2.9.1-x8664, mixed mode) > openSUSE Leap 15.2 x86_64 > -- > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: J L. T. <jlt...@ma...> - 2021-03-12 02:00:41
|
| $ pipe '(end !) literal Works?|console' | 59 +++ _s_2 = () | +++ ^ | +++ Error: Expression expected | Exception in thread "main" java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 | at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64) | at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70) | at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248) | at java.base/java.util.Objects.checkIndex(Objects.java:372) | at java.base/java.util.ArrayList.get(ArrayList.java:459) | at org.netrexx.process.NetRexxC.clgMain(NetRexxC.java:217) | at org.netrexx.njpipes.pipes.compiler.compile(compiler.java:1260) | at org.netrexx.njpipes.pipes.compiler.<init>(compiler.java:1357) | at org.netrexx.njpipes.pipes.runner.main(runner.java:76) According to page 17 of the NetRexx Pipelines Quick Start Guide (Version 4.01-beta3 of December 25, 2020), this ought to work. What am I missing? Leslie openjdk version "11.0.10" 2021-01-19 OpenJDK Runtime Environment (build 11.0.10+9-suse-lp152.2.9.1-x8664) OpenJDK 64-Bit Server VM (build 11.0.10+9-suse-lp152.2.9.1-x8664, mixed mode) openSUSE Leap 15.2 x86_64 -- |
From: Jeff H. <Je...@Je...> - 2021-02-03 22:20:26
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> <p>It appears that a stage name can not have a name that a method has.</p> <p>We have a stage <b>xrange</b> that has worked fine.</p> <p>A month or so ago, I added a convenience method to the <b>utils</b> jar named <b>xrange</b> to match the BIF in Classic Rexx. (NetRexx's <b>sequence</b> works differently if the endchar < startchar.)</p> <p>Now when I run a pipe with a <b>xrange</b> stage (which I am doing to validate 4.00), it gives the error.</p> <font face="monospace">xrange()</font><br> <font face="monospace">^^^^^^</font><br> <font face="monospace">Error: Cannot convert value of type 'netrexx.lang.Rexx' for assignment to variable of type 'org.netrexx.njpipes.stage'</font> <p>So, now I will go back and rename the method to something else. Right now, I think I have used it only once in <b>utils</b>, and of course it is in the documentation.</p> <p>Jeff<br> <font face="monospace"></font></p> <p><font face="monospace"><br> </font></p> </body> </html> |
From: Rony G. F. <Ron...@wu...> - 2020-12-23 16:21:12
|
+1 Congratulations and kudos to you all who made this happen !! ---rony On 23.12.2020 17:07, René Jansen wrote: > For the developers and interested parties: 3.11 has been branched for release. Master branch is NetRexx 4.X, containing 4.01 beta. From this point on, you should be able to develop, build and run with JDK’s =>9. I am running, for example, with OpenJDK 17 ea, and test with 11,13,15 (Amazon Cornetto). The good news is that 4.01 still works with JDK 8, so there is no real need to switch. > > For committers nothing changes, except the version number. Please report any errors or suspected errors so they can be fixed. There have been a large number of changes and although a number of problems was found while testing (and fixed by Marc) it cannot be ruled out that there is more. But all in all I have great confidence in 4.01 beta and I would run it everywhere, except for very important production systems. > > I would recommend a clean clone to avoid any merge problems, although I did one without problems on Linux yesterday, so you can try that first. The bootstrap compiler in 4.01 is already 4.01; the first build needs to be clean, e.g. nothing in build/classes or build/lib. > > best regards, > > René. > > > -- -- __________________________________________________________________________________ Prof. Dr. Rony G. Flatscher Department Wirtschaftsinformatik und Operations Management Institut für Wirtschaftsinformatik und Gesellschaft D2c 2.086 WU Wien Welthandelsplatz 1 A-1020 Wien/Vienna, Austria/Europe http://www.wu.ac.at __________________________________________________________________________________ |
From: René J. <rvj...@xs...> - 2020-12-23 16:08:19
|
For the developers and interested parties: 3.11 has been branched for release. Master branch is NetRexx 4.X, containing 4.01 beta. From this point on, you should be able to develop, build and run with JDK’s =>9. I am running, for example, with OpenJDK 17 ea, and test with 11,13,15 (Amazon Cornetto). The good news is that 4.01 still works with JDK 8, so there is no real need to switch. For committers nothing changes, except the version number. Please report any errors or suspected errors so they can be fixed. There have been a large number of changes and although a number of problems was found while testing (and fixed by Marc) it cannot be ruled out that there is more. But all in all I have great confidence in 4.01 beta and I would run it everywhere, except for very important production systems. I would recommend a clean clone to avoid any merge problems, although I did one without problems on Linux yesterday, so you can try that first. The bootstrap compiler in 4.01 is already 4.01; the first build needs to be clean, e.g. nothing in build/classes or build/lib. best regards, René. |
From: René J. <rvj...@xs...> - 2020-12-21 08:51:24
|
Hi Leslie, In the meantime NetRexx is fiexed to run with the module system, in all modern JVMs. NetRexx 4.01 beta, the first release that can, will be released on the 23rd, so that is wednesday. Drop me a note if you cannot wait for that. René. > On 21 Dec 2020, at 06:31, J Leslie Turriff <jlt...@ma...> wrote: > > Hi, > Perhaps I missed an announcement, but the last I heard NetRexx still needs to > run with Java 8? If I'm wrong about that, where would I find current > installation info? > > Leslie > > > _______________________________________________ > netrexx-pipelines mailing list > net...@li... > https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines |
From: J L. T. <jlt...@ma...> - 2020-12-21 05:31:27
|
Hi, Perhaps I missed an announcement, but the last I heard NetRexx still needs to run with Java 8? If I'm wrong about that, where would I find current installation info? Leslie |
From: Jeff H. <Je...@Je...> - 2020-12-04 21:25:22
|
<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body> <p>I am having a problem with "something" in the NetRexx/Pipelines compile routines. And I have no idea where, much less any solution.</p> <p>I have written a stage DISPLAY, which compiles and works nicely. But it uses both <b>addpipe</b> and <b>callpipe</b>. In order to compile it, using <font face="monospace">pipc</font>, I can not use <b>nrx</b> as the file extension -- it balks at the "<span style="color:#CCCCCC;background-color:#012456;">*in0:</span>" with "<span style="color:#CCCCCC;background-color:#012456;">Error: Unexpected character found in source: ':' (hexadecimal encoding: 003A)</span>"--, but compiles when the same file has a <b>njp</b> extension. From display.njp, the compiled <b>class</b> file works just fine as a stage in a pipe, either from the command line or in another <b>njp</b> file.</p> <p>But the usual <font face="monospace">java -jar ant/ant-launcher.jar compile</font> ignores the <b>njp</b> file.</p> <p>So for an immediate workaround, how can I get the ANT to see the njp-file?</p> <p>Possibly longer term, can we get the compiler work with either file type?</p> <p>This is the code the compiler does not like when it is in a nrx-file:</p> <blockquote> <p> <font face="monospace"> callpipe (display_stage debug 0 )<br> <br> *in0: |<br> fo: fanout |<br> tag {tag} |<br> literal {title} |<br> literal {style} |<br> diskw {fname} ?<br> cmd {fname} ?<br> fo: |<br> *out0:</font><br> </p> </blockquote> <p>Thanks for any help,</p> <p>Jeff<br> </p> <p><br> </p> <p><br> </p> </body> </html> |