The REXX parse statement is not one of its strong points; certainly not in the same league as, e.g., Perl.
There is an old XPARSE (sp?) package that interfaces REXX to IKJPARS; I wish that IBM would provide a supported version, pre3ferably in a new REXX processor incorporating ANSI and OOREXX language levels. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Charles Mills <[email protected]> Sent: Thursday, November 19, 2020 2:30 PM To: [email protected] Subject: Has anyone integrated Rexx with IKJPARS? 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. 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, ... I don't see a good way to parse -- without resorting to a character-by-character loop -- input such as 'now isn''t the time', 'nor, is this', MYTOKEN, YOURTOKEN Am I missing something? It would be great if one could define the expected parameters and their format to Rexx in some systematic way, parse the user's input, and get back either parameter values in stem variables, or an error message to present to the user. Any suggestions? Charles ---------------------------------------------------------------------- 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
