I agree entirely, But: IBM supporting it - that train has left the station around the year 2005. Earlier probably but not so provable or visible as handing over the code. But do we want to be surprised? Yes! I think the Rexx API for SDSF would be fully reusable for an ooRexx - we support the ADDRESS mechanism on all other platforms, someone should start the port with that. If that is still in some CMVC (hint!) we could politely ask to open source that. But otherwise not that hard to reproduce.
The hard problem seems to be that there are no real accessible development environments available - this notwithstanding Moshix’s petition and the visible efforts from some people to try to deliver something usable - what I hear and read is that the new ‘learning’ environment cannot be used for development (only for ‘learning’ whatever that means if it does not have 3270/ISPF interfaces). My customers will not be, in all probability, very happy if I use their time and machinery to compile ooRexx. That leaves us in a bit of a bind. The question arises whether, with no real innovation going on, IBM is prepared to kiss the revenue of the Rexx Compiler (31 bit) goodbye and let the customers discover that shell and Python also run on other machines that don’t have spool or DB2 - these strategy issues always baffle me and I am so happy that is not my profession. I remember IBM telling us 64bit was not needed. And I was there the next year when z/OS became tri-modal and I remember the profound astonishment. I also remember PHP and Swift on the mainframe- that was 2 years ago? (I even remember AD/Cycle, I am that old, and the sound when that was dropped - same sound the jaws of my managers of the time made when they dropped to the floor). So this year I would like to be surprised by the disappearance of covid and a shiny new Rexx implementation where IBM shows it is still the best there is. Like a Rexx compiler for Docker that smokes the competition. Best regards, René. > On 4 Jan 2022, at 15:38, Seymour J Metz <sme...@gmu.edu> wrote: > > Certainly oorexx on z/Linux is useful, and easier than oorexx on z/OS, but it > would be great if IBM would support it cross platform, or at least for CMS > and TSO. > > Both HFS (RIP) and zFS are file systems in the Unix sense, but oorexx only > needs to be aware of the Unix system calls for paths. Of course, classes for > things like SPOOL access would be nice. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of > René Jansen [rene.vincent.jan...@gmail.com] > Sent: Tuesday, January 4, 2022 2:05 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ... Re: Top 8 Reasons for using Python instead of REXX for z/OS > > We have daily builds for ooRExx on Z for Linux on Z on our build machine. > These run on Suse, Red Hat and Ubuntu. JDBC to DB2 works like on every Linux, > to DB2 on z/OS or Linux, Unix, Windows (luw). > There is more on the mainframe than z/OS - although this does not mean that I > would like to see that port. An OO version of Rexx for USS could use the > existing environments for Rexx; the existing OO version of Rexx, NetRexx, > which runs on USS has ‘knowledge’ of conventional MVS filesystems, spool and > other facilities and addressing environments via JZOS. Although, strictly > spoken, ZFS is a z/OS filesystem and the I/O Macros are very alike. > > But I know what you mean and it is a subject of much speculation why Rexx on > z/OS is stuck on 4.02 - or is it? > > Best regards, > > René. > >> On 4 Jan 2022, at 14:15, Jeremy Nicoll <jn.ls.mfrm...@letterboxes.org> wrote: >> >> Presumably an ooREXX compiled under SUSE Linux gives one something >> with no knowledge of, for example, z/OS file systems, let alone any of the >> environments supported under TSO REXX. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
