AFAIK those are all environments and function packages rather than part of REXX, so they should seamlessly plug into a port of oorexx. I believe that you would need 31-bit stubs for the 64-bit interface of oorexx 5.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Farley, Peter x23353 [0000031df298a9da-dmarc-requ...@listserv.ua.edu] Sent: Tuesday, January 4, 2022 6:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ... Re: Top 8 Reasons for using Python instead of REXX for z/OS Also MVSVAR, OUTTRAP, STORAGE, SYSCPUS, SYSDSN, SYSVAR if equivalents are not already supplied in oorexx. Access to such data as is returned by MVSVAR. SYSVAR, etc. could conceivably be made using reads of pseudo-devices such as "/dev/$$REXX$$/SYSPROC/finer_addressing_here" but OUTTRAP, STORAGE and SYSDSN are useful and frequently needed (again barring already existing equivalents in the implementation). Binary reads should return binary blobs of whatever the system I/O interface returns (RECFM=U as well). Parsing the resulting binary blob is the programmer's responsibility. Obviously some facility for reporting back the actual byte length of the returned blob is necessary. I always preferred EXECIO nnn to * or 1 where REGION was sufficiently available. I have processed multi-million record files without issue and with reasonable performance using EXECIO 100000 or more each time in a loop, where the actual count that I coded varied depending on the average actual expected record size. SYSCALL and SDSF could be part of " MVS/TSO/etc." that I wrote. And don't forget the FTP Rexx interface that I am told exists (though I have never tried it myself, mind you, at least not yet). Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Tuesday, January 4, 2022 5:43 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ... Re: Top 8 Reasons for using Python instead of REXX for z/OS On Tue, 4 Jan 2022 19:18:09 +0000, Farley, Peter x23353 wrote: > ... And of course full ADDRESS MVS/TSO/etc. support as well. > Why is TSO needed? TSO-specific facillities such as: o LISTDSI? o TRANSMIT/RECEIVE I've used the ADDRESS TSO surrogate for some of this, even to run non-interactive ISPF LM. (PITA to allocate required data sets.) <https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/2.1.0?topic=processing-tso-command-environment__;!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!dDfUQ6NHI3eU-wslfshP9AZWLZAYPld61bkPqQLflCXUA-YgKTTNzi9DrH4YWSAsc0enEg$ > On Tue, 4 Jan 2022 19:29:27 +0000, Seymour J Metz wrote: > ... >I would expect IBM to functionally stabilize EXECIO unless there is something >that it does better than stream I/O. > How might stream I/O deal with RECFM=V binary files, particularly containing '15'x among the data? Many programmers insist on the superior performance of EXECIO * over EXECIO 1 in a loop probably due to CALL/RETURN overhead. linein() in a loop might suffer similarly. ADDRESS SDSF API provides generated DD NAMEs for spool files. I've used these overriding IEBGENER SYSUT1. I could imagine overriding SYSUT2 with a pipe which could be read by linein(). Spool access from available parts. (Subject to port of ADDRESS SYSCALL and ADDRESS SDSF.) -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
