> It's the UNIX tradition. https colon//www.goodreads.com/quotes/353571-a-foolish-consistency-is-the-hobgoblin-of-little-minds-adored
"When the only tool you have is a pipe, everything looks like a filter." > Likewise, is there no compelling need for IRXJCL? Can you pipe the output of a Unix command to IRXJCL? shell syntax? Can you pipe the output of a Unix command to IRXJCL with shell syntax? Is there a compelling need to do that? > And, yet if bar is marked executable and has the Rexx > magic number, > and is in PATH, foo | bar simply works. So does foo | rexx bar, but neither one treats the output of foo as Rexx code. > It makes most sense if someone else writes that wrapper. You are someone. -- 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 3:42 PM To: [email protected] Subject: Re: Scripting REXX thought -- inspiration or insanity? On Mon, 16 Mar 2020 19:11:00 +0000, Seymour J Metz wrote: >The Rexx language processor is intended for scriften would you neepts that >drive the CLI. >I don't see a compelling need for it to accept input from stdin. > It's the UNIX tradition. Likewise, is there no compelling need for IRXJCL? >How often would you need somthing like foo | rexx bar? > And, yet if bar is marked executable and has the Rexx magic number, and is in PATH, foo | bar simply works. >IMHO it makes more sense to write a wrapper tailored to a specific >requirement. >What are the issue with using an in-storage procedure? > It makes most sense if someone else writes that wrapper. Perhaps something that reads a file into storage and invokes the Rexx API. -- 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
