> ANSI standard Rexx. But IBM hasn't recognized that the century > has passed when IBM could flout industry standards when it > couldn't drive them. CMS Rexx has incorporated CHAROUT and > its ilk. TSO Rexx has not.
Yes and no. REXX in z/OS is part of TSO/E and runs in several different environments. TSO/E REXX running in the TSO environment does not support ANSI stream I/O, but in the Unix environment the same REXX does support it. Only IBM knows why. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Paul Gilmartin [0000000433f07816-dmarc-requ...@listserv.ua.edu] Sent: Monday, March 23, 2020 11:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Does anybody remember CLIST? On Mon, 23 Mar 2020 00:28:16 -0400, Bob Bridges wrote: >Gil, I can't tell whether you're suggesting more things that CLIST can do that >REXX cannot, or things that REXX can do even though I said it cannot. > A mixture; some of each. >a) I don't know what CHAROUT is, but it sounds like the same issue as WRITENR. > Or are you saying it's some sort of REXX function that can imitate CLIST's >WRITENR? > ANSI standard Rexx. But IBM hasn't recognized that the century has passed when IBM could flout industry standards when it couldn't drive them. CMS Rexx has incorporated CHAROUT and its ilk. TSO Rexx has not. https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.bpxb600/charo.htm Not to have made this part of the z/OS Rexx base for roughly the same amount of effort is a malign instance of NIH; Conway's Law. >b) I don't know what "RYO" is either ("rite your own"?), "Roll Your Own". Akin to "DIY". > ...but unless I'm thinking of something different, RXSOCKET isn't trick > CLIST can do that REXX cannot; I used it to write a socket server (and a > separate client) in REXX. And > Me, too. An HTTP client on CMS; later converted to the friendlier CMS Pipelines. >c) TSO EDIT isn't an exception to what I wrote, it's a perfect example of #2 >below, a subsystem that CLIST can interact with dynamically (if that's the >word) and REXX cannot. Exactly what I was talking about, although I used FTP >as my example because FTP is what I've encountered most recently. I haven't >used TSO Edit in ... well, must be the early '80s at the latest, maybe the >late '70s. > Yes, an example. CMS EDIT (but not XEDIT) has a similar relationship to CMS EXEC but not EXEC2 nor Rexx. -- gil ---------------------------------------------------------------------- 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
