> Dammit!  Regina gets it right.

No - the syntax that you are using pertains to the shell and will work with any 
command that expects input from stdin. It's called a here document.

>Why doesn't z/OS have a REXX command?  Why can't
>IRXJCL accept >a script in SYSIN?  (There's a bizarre 
>cheat; unsupported.)  Why doesn't >OMVS Rexx have a 
>REXXPATH environment variable to search for
>external functions (and another for function packages)?

Have you submitted an RFE?

>I do not consider Rexx a candidate for a shell,

Who claimed that it was? Like CLIST, EXEC and EXEC 2, it was intended as a 
scripting language and, IMHO, is well suited for that purpose, although there 
are some enhancements that would make it a better scripting language,

>it allows (sometimes requires) a function's definition >before its use, 

WTF? REXX function are normally written after their use, for very good reason. 
The one exception is that when one function calls another it doesn't matter 
which comes first.

>Why does the Rexx standard not provide a means for >PARSE EXTERNAL to report 
>end of input (e.g. SYSTSIN)?

What is queued, chopped liver?

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Paul Gilmartin [[email protected]]
Sent: Monday, March 16, 2020 12:31 PM
To: [email protected]
Subject: Re: Scripting REXX thought -- inspiration or insanity?

On Mon, 16 Mar 2020 15:57:19 +0000, Seymour J Metz wrote:

>I have a terrible hammer; every time I use it with a screw, I have problems.
>
>REXXTRY is an extraordinary tool for what it was designed to do - it is not, 
>and was never intended to be, an IDE. It is simple and elegant.
>
>If you need a log for your REXXTRY session, it's a simple matter to add that 
>functionality.
>
I use script(1) if my terminal emulator doesn't maintain a log.

>Likewise allowing a statement as an argument. Of course, much of what you want 
>you can do with redirection without having to touch the code ("When the only 
>tool you have is a pipe, everything looks like a filter.").
>
Dammit!  Regina gets it right.  Example:
    532 $ regina /dev/fd/3 3<<endrexx
    > trace R
    > parse version .
    > endrexx
         2 *-* parse version .
           >.>   "REXX-Regina_3.9.1(MT) 5.00 5 Apr 2015"
    533 $
(I've used this to embed Rexx in a shell script.)

Why doesn't z/OS have a REXX command?  Why can't IRXJCL accept
a script in SYSIN?  (There's a bizarre cheat; unsupported.)  Why doesn't
OMVS Rexx have a REXXPATH environment variable to search for
external functions (and another for function packages)?

I do not consider Rexx a candidate for a shell, first because it allows
(sometimes requires) a function's definition before its use, with the
consequence that a typo in a function name causes the interpreter to
devour input indefinitely.

Why does the Rexx standard not provide a means for PARSE EXTERNAL
to report end of input (e.g. SYSTSIN)?

-- 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

Reply via email to