I could ~really~ wish Regina, or at least some version of REXX, was more widespread on PCs. Some years ago I overheard my boss talking on the phone about a problem which I then solved for him using Regina. (It involved parsing several megs of firewall logs looking for particular types of errors; the REXX solution took seconds instead of a couple hours.) But for the most part, I figure whatever solutions I write for clients should use tools they already have at hand: VBA for Excel, for instance, REXX for the mainframe and so on. If they have to acquire a new and let's not forget untrusted tool even to get started on the solution, they're much less likely to benefit from it.
For the same reason I have long left unsatisfied my ardent desire to try out ooREXX. I may use it for my own solutions, but most of my work is done for others...which after all is as it should be. Sigh. --- Bob Bridges, [email protected], cell 336 382-7313 /* When their love was strong they could sleep on the edge of a sword, but now when they have forgotten, a bed sixty feet across is not sufficient. -Rab Akiva, quoted in _The Source_ by James Michener */ -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Monday, March 16, 2020 12:31 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.) --- On Mon, 16 Mar 2020 15:57:19 +0000, Seymour J Metz wrote: >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."). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
