Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes

[<hp...@we...>]

Following append bounced,

> reason: 550 Blacklisted file extension detected

So once more without the ZIP -- René, IMO you got it in your
personal mail, holler if not.
/M.

Am 02.06.2022 um 14:58 schrieb hp...@we...:
> Hello René!
>
> In chapter 3.4 of the NetRexx QuickStart Guide the shown subdir
> separator is a "normal" slash (/) while Windows uses instead the
> backslash (\). Must I convert it to slash or may it stay as is?
>
> Step 3 in same chapter advices to add another path+fileID to the
> CLASSPATH variable. Alas it does not mention if and if yes how to
> separate the two data, by blank, by semicolon, or something else?
>
> There is no file [...]/lib/tools.jar in lib subdir. There is no
> file tools.jar in any subdir of NetRexx. There is no such file in
> the "Java tree" (assumed this is the installation folder). So
> chapter 3.4 step 3 remains undone (until further advice).
>
> NetRexx QuickStart Guide chapter 3.5, Installing just the NetREXX
> Runtime, second paragraph states "To do this, follow the
> appropriate instructions for installing the compiler, ..." Where
> do I find the appropriate instructions for installing the
> compiler? Under 3 "Installation" there is just 3.4 "Installing the
> NetREXX Translator" and 3.5 "Installing just the NetREXX Runtime",
> but nothing like "Installing the Compiler". Or was the compiler
> renamed to "translator"? Pls advice.
>
> NetRexx QuickStart Guide chapter 3.7 "Testing the NetREXX
> Installation", step 1, the command
>
>> java org.netrexx.process.NetRexxC hello
>
> fails. Closing the cmd window and starting a new one cures it.
> Seems changing the CLASSPATH variable needs kind of power-cycle.
> Alas...
>
>> Program hello.nrx
>>  1 +++ say ?hello, world?
>>    +++     ^
>>    +++ Error: Unexpected character found in source: '?'
>> (hexadecimal encoding: 2
>> 019)
>> Compilation of 'hello.nrx' failed [one error]
>
> Again a 'nonconformance' by edit-copy/edit-paste from Adobe. (BTW,
> there are some places in the QuickStart Guide where it works.)
>
> Same chapter. After step 1 worked, at least last line showed
>
>> Compilation of 'hello.nrx' successful
>
> and there is now a file hello.class in the subdir, step 2 fails:
>
>> Fehler: Hauptklasse hello konnte nicht gefunden oder geladen werden
>
> Chapter 13 "Troubleshooting" reveals, CLASSPATH variable must
> contain a point. I prefix its content by '.;' (w/o quotes)
> _assuming_ the semicolon could be the correct delimiter. Closing
> the cmd window, starting a new one, now step 2 of chapter 3.7
> works right away.
>
> Recently you said,
>
>> NetRexx does not have an ‘installation procedure’ as such...
>
> Well, since the NetRexx 'installation' seems a bit more than just
> to unpack a zip file, it could help a lot. Frankly, at the moment
> I have some trouble to stay polite. This kind of installation
> instruction with its widely distributed information is quite
> unpleasant. For sure not a smooth cakewalk.
>
> Ok, I now made my way through chapter 3 of the QuickStart Guide.
> Is there more in it I need to know/install/observe for running
> pipelines? I continue with next "little setup", chapter 3.1 of
> NetRexx Pipelines Guide and Reference.
>
> Seems as Windows user I should read this bottom-up, then I have to
> do nothing since NetREXXF.jar is prefixed to the CLASSPATH content
> in pipe.bat as in pipc.bat too. Both are in the bin subdir which I
> added to the path yesterday. But (!) I renamed PIPE.BAT to
> HIPE.BAT to avoid interference with OS/2 Pipelines (which I
> currently _do not_ uninstall). Do you see more pitfalls in this
> respect?
>
> Test:
>
>> C:\prgm\NetRexx>hipe "gen 100 | dup 999 | count words | console
>> 100000
>
> Works :)
>
> So it seems I have done all preparations (at last) to start our
> experiment. Did I miss something? Yes, up to now you only have the
> source file and a description in brief. There are few more files
> you need to run VilMA. Find attached a ZIP with all you need in
> case you have OS/2 Pipelines. It also contains (besides a compiled
> ooRexx) a more detailed description about what to do with VilMA.
>
> I suggest I copy my program to a new directory and replace
> pipeline by pipeline according your advice until all are done.
> Because I renamed pipe.bat a coexistence of NetRexx- and OS/2
> Pipelines might be possible and therefore also an incomplete
> migration could work as usual.
>
> /M.