You may be right; I was unable to find a copy of the pertinent Rexx 
User's Guide from 
that period, though
http://www.rexxinfo.org/All%20IBM%20Rexx%20manuals/ALLIBM_1.HTM
purports to provide such.

Leslie

On 2021-02-10 04:30:20 René Jansen wrote:
> Hi Leslie,
>
> I am sure you mean 1984. And then there was still only EXECIO. I have to
> look up when VM/CMS got stream; TSO never had it until now, unless we
> installed a library. I will try to find out the timeline.
>
> best regards,
>
> René.
>
> > On 10 Feb 2021, at 05:45, J Leslie Turriff <jlturr...@mail.com> wrote:
> >
> > On 2021-02-09 19:02:12 Michael Lueck wrote:
> >>> Any ideas on how this was meant to be when it was designed?
> >>
> >> I never claim to be the best expert at REXX history, however...
> >>
> >> On Mainframe, I believe either the Stream concept came much later or
> >> still is not there at all.
> >
> >     The file I/O functions [stream(), charin(), charout(), chars(),
> > linein(), lineout(), lines()] have been in the language since at least
> > when I first used VM/CMS in ~1974. They could operate on CMS minidisk,
> > Shared File System*, or Byte File System* files; sockets capabilities
> > came later when a TCP/IP stack was added to VM.  In MVS Rexx could use
> > these functions to do I/O to QSAM, Open Edition or Unix System Services
> > files. See https://www.vm.ibm.com/library/640pdfs/64622201.pdf Chapter 9:
> > Input and Output, for example.
> >
> > Leslie
> >
> >
> > --
> >
> >
> > _______________________________________________
> > Oorexx-devel mailing list
> > Oorexx-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel


-- 


_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to