PMFJI here, but IMHO the pipeline paradigm, though obviously powerful and useful, is not the major advantage of VM and CMS over z/OS and TSO for developers, Rexx or otherwise.
Rather, I would argue that it is the even more the powerful concept of DVM's, Disconnected Virtual Machines, and the resulting ability for even ordinary application developers, not just sysprogs, to very simply arrange to pass data between them via VMCF and/or IUCV. Then add the power of VM Rexx and pipeline support and XEDIT and the other CMS tools as the only code needed to actually run in and interact with those DVM's and many extremely useful and powerful applications can be coded with nary a compiler or assembler in sight, never mind in use. No authorized coding or cross-memory complexity required. Add DB2 and networking support for Rexx and many full-function business applications are added to the possibilities. I bemoan the failure decades ago of the CMS on MVS project. That would, indeed, have changed the history and practice of our computing lives. And a Happy New Year to all. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of David Crayford Sent: Sunday, December 29, 2013 11:21 PM To: [email protected] Subject: Re: Learning Rexx On 29/12/2013 1:07 AM, Paul Gilmartin wrote: > On 2013-12-28, at 09:47, Charles Mills wrote: > >> Actually CMS on VM better for rexx than z/OS. >> > Why? (Risking an advocacy thread.) > > For me, one reason is the CMS HELP facility. In fact, > sometimes coding Rexx for z/OS I'll log on to CMS merely > to use HELP REXX <instruction>. > > Other reasons? Most VMers claim that Rexx is superior on VM because of CMS pipes. That's a pretty strong argument. -- 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 [email protected] with the message: INFO IBM-MAIN
