From: <hp...@we...> - 2022-06-22 12:23:17
|
Like some more? > D:\PRGM\NetRexx\examples\MkROM>nrws > Workspace for NetRexx 4.04 build 272-20220524-1803 > Copyright (c) Martin Lafaix 2000 > Copyright (c) parts RexxLA 2019,2021 > pipelines processor loaded > Ready; pipe (sep !) literal abc!dup 5!a: count lines!term?a:!insert /Count: /!term 1.921 s > 56 +++ _s_2 = a:!insert() > +++ ^ > +++ Error: Unexpected character found in source: ':' (hexadecimal encoding: 003A) The problem might be the sep option. === Now a "real world example" -- one pipe, two issues: > address '' ripe '"(MkR_5 sep !) cons!reverse!fblock 1!', > 'xlate 1 00-FF 3A 20-3F 20-3F 40-5F 00-1f 60-66 40-46!', > 'spec 1 c2d!term', > with input using (modid) output stem ronam. With modid = 'C PPC 1981' the output is ronam.0 = 10 and ronam.1 .. 10 is void, empty, zilch. In contrast to CMS Pipelines the spec stage requires "the position of the field in the output record." Thus using 'spec 1 c2d 1' -- first issue solved, next please! -- the output ronam.1 .. 10 is now 32, or blank in other words. In contrast I expected 49, 56, 57, 49, 32, 3, 16, 16, 32, 3. Seems Xlate fails. === Question: Is it possible to transfer arguments to compiled NetRexx pipelines? Example: i and fx are integers > 0 > address '' ripe '"(MkR_s1 sep !) cons', /* connect to input */ > '!drop' i, /* from not possible */ > '!take' fx, /* take n bytes */ > '!spec w1 x2c 1', /* convert to characters */ > '!join *', /* make it one line */ > '!term', /* keep result */ > with input stem prgm. output stem pt2. Compiling corresponding .njp shows no error, alas execution fails. Best, M. |