That is actually part of the Rexx library supplied as part of the Rexx 
compiler.  I have used it quite successfully without needing SIGNAL ON 
NOTREADY, though I do not need ZFS/HFS file access for my application purposes, 
only classic MVS datasets.

Implementation of standards is only useful if the feature is really needed.  I 
can't think of a reason for needing NOTREADY with classic datasets on z/OS when 
SYSDSN will tell you whether the file is available or not.

Just my opinion of course.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Paul Gilmartin
Sent: Monday, July 01, 2013 9:48 AM
To: [email protected]
Subject: Re: EXECIO - Was: Great quote on http://slashdot.org (changes 
frequently)

On Mon, 1 Jul 2013 09:25:37 -0400, Shmuel Metz (Seymour J.) wrote:

>In <[email protected]>, on
>06/30/2013
>   at 09:50 PM, Paul Gilmartin <[email protected]> said:
>
>>What are the enhancements in the ANSI standard?
>
>Among other things, stream I/O, enhancements to address.
> 
I believe stream I/O was part of MFC's original specification of Rexx;
it can hardly be called an "enhancement" in the ANSI standard.

Which enhancements to "address"?

>Oddly enough, z/OS supports stream I/O in the Unix shell but not in
>the TSO TMP.
> 
Not really.  I believe an enthusiastic and generous developer provided
part of stream I/O as a function package.  But it lacks SIGNAL ON
NOTREADY, which can't be implemented as an external function.

And if one looks hard enough in IBM sites, one can (once could?) find
YA function package which provides stream I/O for legacy data sets
but not for UNIX files.  Perhaps it belongs to the Rexx compiler.

    http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/H1981605/3.0
     Stream I/O for TSO/E REXX

in:

    Title: IBM Compiler and Library for REXX on zSeries V1 R4 User's Guide and 
Reference
    Document Number: SH19-8160-05

(also lacks SIGNAL ON NOTREADY)

And of course one _can_ get to UNIX stream I/O under the TSO TMP
if one resorts to "address SYSCALL spawn".

--


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

Reply via email to