> Usuing any UNIX facility causes the task to be dubbed with the UID in the > owners OMVS segment, a generated unique UID, or (obsolete) a default UID.
None of which is relevant to whether the OMVS segment is required to use the OMVS command. > Have you a better citation? For what? The ANSI standard is the correct document for ANSI REXX. Has IBM claimed that TSO/E REXX running in Unix System Services is ANSI compliant? If not, then Using REXX and z/OS UNIX System Services is the only relevant document. > What should LINEIN() do to distinguish an empty line from end-of-file? Whatever the language reference specifies. If it claims to be ANSI compatible then it should raise NOTREADY. > I've used implementations where the STREAM() function makes the distinction. Probably Regina, which *does* claim to be ANSI compliant. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Thursday, September 12, 2019 8:58 PM To: [email protected] Subject: Re: Submitting batch if you don't have TSO > On 2019-09-12, at 14:26:36, Seymour J Metz wrote: > >> This implies that submitter must have an OMVS segment. > > No. If he can run in a Unix shell than he can use the Unix functions for REXX. > > I looked at Chapter 2. OMVS, a 3270 terminal interface to the z/OS shell in > z/OS: UNIX System Services User's Guide and didn't see anything about > requiring an OMVS segment. It's possible that you need an OMVS segment to use > the OMVS command, but that's certainly not implied by the functions for RXX > under a Unix shell. > Usuing any UNIX facility causes the task to be dubbed with the UID in the owners OMVS segment, a generated unique UID, or (obsolete) a default UID. >> And it was done as a function package, so SIGNAL ON NOTREADY is not >> supported. > > The ANSI specifications call for returning an empty string rather than > raising a signal. But I wonder whether IBM would accept an RFE to allow > external to raise a signal. > I find NOTREADY in the Preliminary ANSI Standard at: http://secure-web.cisco.com/1-6aKvuClnCXSaxxzypslqut6oQBsNlDbLOSGFnoNtKZ1U3AbH1IRdfBoQ_Ghxdm44mcFIgp7cj0accJstzQ_P42beELAo55el1sMRzbdC2fwS25mdNEz60nL78znAnI390-tQrItkVfwaEuYFrZfh57-3egYAHsdIBCb6xn7H7-6ozLl8ZVZYqSDxVxmPX9UAr8pc7UdjJEHtRowr4BcmxjblUMsqSOVrjE1p0xZfO4hv61Z368GvbC7g-nwQLJNQI7fYwSGPzbuDXwGvsQ3TLdOGU0XaeqL1UQEzHYWp-VC9TJN9cseRpT3pMDvtlmNEET46ycVcvPpPIOBnCx2Y2rBIJC1mKn0iuYVaEZu0EE1f3HEnEn0sNNxaiyq9_p3cDTAkvdMH2FQ7VdcZ7Guu0A1ydN72NPNovyOZOASPoAfmFsld1FiXUsLJ2kGZKcL/http%3A%2F%2Fwww.rexxla.org%2Frexxlang%2Fstandards%2Fj18pub.pdf Have you a better citation? What should LINEIN() do to distinguish an empty line from end-of-file? I've used implementations where the STREAM() function makes the distinction. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN I documentation describes the ANSI standard; does IBM complain the the stream I/O for REXX in Unix System Services is ANSI compliant. If not, then ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
