Not sure we got here from 'PLI', but so be it. I was deeply embedded in CLIST writing by the time REXX made its way to TSO/E. Here are a few points I haven't seen from others.
-- CLIST was modeled or at least inspired by the TSO command processor. That's the framework that handles most 'native' TSO commands. Very few customers these days write or even modify TSO commands. The framework is well documented and supported by a host of macros and load modules. It's very powerful but very complicated for someone who doesn't do it regularly. -- Because of this historical connection, 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. On Wed, Sep 29, 2021 at 2:07 PM Charles Mills <[email protected]> wrote: > That's why we get the big bucks. > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Wednesday, September 29, 2021 11:01 AM > To: [email protected] > Subject: Re: PL/I vs. JCL > > On Wed, 29 Sep 2021 10:48:53 -0700, Skip Robinson wrote: > > >Is that operand required? > > > Only sometimes. IBM made it as complicated as possible: > > > -- Skip Robinson 323-715-0595 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
