On Sun, 22 Jun 2025 12:01:01 +0200, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote:
>> I've never found any doc for defining environments within OOREXX. OOREXX >> design is the compatibility challenge that requires OOREXX changes. > >You can consult the documentation coming with the ooRexx documentation book >"rexxapi.pdf", section >"1.16. Command Handler Interface" (this is the powerful native API of ooRexx), >but also sections >"2.4. Subcommand Interface" (SAA) and "2.6. Registered System Exit Interface" >(SAA). rexxapi.pdf was not listed on the documentation page. >If you use the ooRexx-Java bridge (BSF4ooRexx) then you can implement Rexx >command handlers simply > >BTW, as BSF4ooRexx is a fully bi-directional language binding it can be used >to create Rexx command >handlers even in - ooRexx (without any Java skills) ! :) This discussion is about making OOREXX available for more than z/OS batch and Unix. Implementing scripting languages designed for Unix are daunting for complex z/OS environments (e.g. TSO, CICS, IMS, Tivioli and more). A Unix process is not a TSO address space with multiple activities. It's not a CICS or IMS transaction. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
