I tend to use Perl when I need to do complicated parsing of strings. Java, Python and Ruby have similar capabilities in that regard.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Bob Bridges [robhbrid...@gmail.com] Sent: Thursday, September 30, 2021 7:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I vs. JCL I once wrote an external routine that can break a character string into various individual parms and return them on the stack. It correctly parses strings with quotes, parens and comment markers. But as you say, even I hardly ever use it. Most routines work perfectly well with a string of one-word arguments, and if I don't have to remember what order they come in and don’t have to label them, anything more is almost never required. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Having your book turned into a movie is like seeing your oxen turned into bouillon cubes. -John LeCarré */ -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Skip Robinson Sent: Wednesday, September 29, 2021 18:06 ....one of the most powerful features of CLIST is the mechanism by which parameters/options are passed by the user: positional or keyword, required or optional, with system prompting. I once saw a REXX routine that simulated the old command/CLIST parm processing. It was very complicated and hardly worth the trouble IMHO. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
