No argument. Still, it's hard to beat the flexibility of TSO/CLIST parameter handling. I wrote a TSO command once partly for kicks. Really complicated. Pointers to pointers to pointers. When it was done, it was super easy to use. Sigh.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jeremy Nicoll Sent: Thursday, November 19, 2020 12:12 PM To: [email protected] Subject: (External):Re: Has anyone integrated Rexx with IKJPARS? *** EXTERNAL EMAIL - Use caution when opening links or attachments *** On Thu, 19 Nov 2020, at 19:30, Charles Mills wrote: > It would appear to be a lot of work, but it would seem that "TSO > format command parsing" and Rexx would be a natural marriage. > > I have never used IKJPARS, so I don't claim to be an expert, and > others might disagree. Surely very few people use command line TSO though? Isn't it more common if there's something complicated to do to offer the user an ispf panel (which will remember previous parameter choices) to set up the options they want? Also, even if you do make TSO REXX IKJPARS-capable, all you're doing is making REXX inconsistent across all the different subsystems that it's usable in. > The issue I am struggling with is that for all of Rexx's parsing > power, which is of course legendary, it does not seem well-suited to classic > "MVS" > (for want of a better term) quoted strings. I am considering an EXEC > that would accept parameters of > > 'a quoted string', 'another quoted string', simpletoken1, simpletoken2, ... Why do you need quoted strings? Something I do in some situations is make the very first character of an arbitrary string a delimiter, and then wherever that same character appears later on, the string gets chopped up on that. So > 'now isn''t the time', 'nor, is this', MYTOKEN, YOURTOKEN might become !now isn't the time!nor, is this!MYTOKEN!YOURTOKEN (I also sometimes have an escaped blank character so that an exec that expects a single token as its argument could be given !the!meaning!of!life but still process that as "the meaning of life". Or I pass tokens which are: c2x(whatever) -- Jeremy Nicoll - my opinions are my own. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
