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

[René J. <rvj...@xs...>]

Hi Mike,

do OS/2 Pipelines an sich still work? As I understand for a long time OS/2 16 bit code was still supported under NT and successors - the 16bit code being OS/2 1.X and supported by MS. If this went away, it becomes harder - not impossible due to QEMU/UTM, Virtual Box and the likes. If you can still run 16 bit OS/2 executables with Windows 10, this is a PATH/DLL/loading problem. ooRexx uses address which can execute a shell in addition to a lot of other platform programs. If things stop with ooRexx 5.0.0 it can be fixed - dlopen() etc still work, maybe some linkage conventions are changed.

Mark should be able to help with Rexx/gd. This might be the RexxSAA.h thing that happened a few years ago. I cc’ed him because I do not think he is on this list. But it should be working.

These are of course things that complicated matters; easiest would be just to do NetRexx with its pipes and a Java Swing or JavaFX interface. The Java Properties class is made for picking up parameters, and it is easiest to use those in a Java (NetRexx) program instead of marshalling them to ooRexx. 

But I like complicated matters so just go agaed, and I am sorry I don’t have enough time as I would like to invest in this. There is also some code to write for the day job, and also NetRexx and CREXX are time intensive.

Maybe we can ask Jeff to have a look at SPECS and its missing parts. At the moment I am trying to harmonize all the ways you can execute a pipe.

About OS/2 Pipelines - who did that, do we have source? Is/was it IBM internal, EWS? Would someone invest the time in open sourcing it? The ooRexx pipe stuff is interesting on the concept level - it is nowhere near the NetRexx Pipelines functionality compared to CMS/TSO Pipelines, and that was a lot of work, even if you take into account what Ed and Jeff already had 20 years ago.

Your perspective of having to convert *all* the pipelines is actually more fun to me, as it gives the opportunity to fix a lot of things in Rexx and Pipelines. Only it will take a lot longer.

best regards,

René.

> On 14 Jun 2022, at 13:01, hp...@we... wrote:
> 
> Hello René!
> 
> The plan to migrate OS/2 to NetRexx Pipelines one by one while due
> to access to both the program still works as a whole -- this plan
> is thwarted since at a sudden OS/2 pipelines is not accessible any
> more from ooRexx 5.oo under Windows 10. I have no clue why, even a
> power cycle did not cure it.
> 
>> call RxFuncAdd 'RxPipe', 'RXPIPE', 'RXPIPE'
> 
> just fails. But also loading the Rexx/gd library:
> 
>> Call RxFuncAdd 'GdLoadFuncs', 'rexxgd', 'GdLoadFuncs'
> 
> in another program fails. While
> 
>>  rc = RxFuncAdd("SockLoadFuncs","rxsock","SockLoadFuncs")
> 
> still works.
> 
> So I _do have_ to convert all OS/2 pipelines and may test the
> program in full only when completed the last one. Same task but
> less fun.  (In contrast, inaccessible Rexx/gd library is a
> substantial loss.)
> 
> Best,
> M.
> 
> 
> Am 07.06.2022 um 21:59 schrieb René Jansen:
>>>>> [...]
> 
> 
> _______________________________________________
> netrexx-pipelines mailing list
> net...@li...
> https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines