> Are you thinking of constructs such as:
'ADDRESS' taken_constant [expression] [ 'WITH' connection]]
Yes. Specifically, WITH input_redir [output_redir] [error_redir] .
> Pointless for CMS or TSO since the concept of standard input/standard output
> is alien to each.
Perhaps pointless for CMS, but the TSO stack has all of the necessary
facilities. TSO commands do not normally BSAM/QSAM or TGET/TPUT for line mode
terminal I/O, but use service routines.
> Perhaps from Amiga? OS/2? AIX? SAA?
Certainly not from OS/2 or SAA, since they don't have that facility. OS/2 uses
RXQUEUE and pipes for capturing command output, e.g.
'DIR FOO.* | RXQUEUE'
Will put the file list in the stem associated with the active queue.
--
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, January 17, 2019 11:13 PM
To: [email protected]
Subject: Re: Unreadable code (Was: Concurrent Server Task Dispatch issue
multitasking issue)
On Tue, 15 Jan 2019 22:57:28 +0000, Seymour J Metz wrote:
>IBM never upgraded TSO/E for the REXX standard. I see nothing in z/OS TSO/E
>REXX Reference Version2 Release3, SA32-0972-30 about built-in variables TRUE
>and FALSE.
>
>More important, IMHO, is that IBM did not add the ANSI extensions to ADDRESS.
>>
>>http://secure-web.cisco.com/1ps8-jjITHM7k061aRsyP3fh7U59UdoVF9jCt1fPQ8_dweSsiSJqCd8sbAmQMpHeP3JSkqDOolCGSWsfeCEO_Y-MZtYSJCA8dwNbQ15TUjUYsi1rc1iV7yP9xIPXccg2LA_VLjlsHYkPODSd0-c6Fefjs9pbMZZLU-T0nl9Dz8JKqFLOKZtn_6VAzD47F1DpreW1rg-731MHOa3jVSYxGeJlPPc_soNCExHxZbsiYaSogAF0uLxjycVhm_pKwe9Thkf7Aa79emOg4o73k3NX3Ira_sSYTXGLXLIUQVV9x1osIrhh6TgQ2ERsW7idqwCptNLiWWQtJc1zzj19yytmcPPtKJJ_ThzeGnMnQWV5q2igUeNN-8Z6UfPs4GNY-wMzhWN3B515CJeSyXCzn5Qo63CoruahQy_LtecEgKEAg0NgDqy_gHCYk6HepOHLcNpVz/http%3A%2F%2Fwww.rexxla.org%2Frexxlang%2Fstandards%2F
>> has ordering information and links. At $125, I'd just go for the draft, but
>>it's probably worth it if you're trying to implement ANSI-compliant Rexx
>>(sic).
>>
>(direct link:
>http://secure-web.cisco.com/18067JUtGA2FTOLLVQ2xoU5reLnjtcqfCMB4Zd392u73EzngVkpfI-8Yxc0gtDZ_GYtMieVO3mvl2qjqHzRmoFpHNClDcp-bVi5cNaZKT3RwfDoanek5Oj-rR8wVkkkTZ2zmoWlDcGqcgw3ivEwRHWnEvR5He5vJvUBdOUCkLvup6aH2yWkJcJfyBym-3kEMDW6LKLhXJvY0qsGkVkJoxb-G9sjieiFKU_An13kqMX25KGU9PTnfuB9xo1XvwLXNhgBr4MlmccL5C7J4hlAd8ROJpTOqRzYLtTGemhDD0PVAEYjuEETS3Q3S7zTq4BFVO7WQWtQ-0PDRhFa9FBTkPC-A3gJov3SMVfyKt9TwazzqKAI3lNoqgpLRIuvNcZKZoMisvDt4evC1QOgPoh2HCqiRKsoMECrLFGOm7sM3Ec-Jd0ReT-mUcbk3LNJ-PQi5c/http%3A%2F%2Fwww.rexxla.org%2Frexxlang%2Fstandards%2Fj18pub.pdf
>)
Are you thinking of constructs such as:
'ADDRESS' taken_constant [expression] [ 'WITH' connection]]
Intriguing. Seems to be specifying redirection. Pointless for CMS or TSO
since the concept of standard input/standard output is alien to each. Relevant,
of course, to OMVS, but OMVS was unable to exert much influence on the
design of z/OS Rexx.
I wonder how this made its way into the Standard since standards tend to
be descriptive and rarely innovate extensions except to resolve ambiguities
or inconsistencies.
Perhaps from Amiga? OS/2? AIX? SAA?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
