I forgot a point I meant to make in this reply. We discussed how to run CLIST or REXX directly from a source PDS without benefit of SYSPROC or SYSEXEC. There are several products in a z/OS configuration that are delivered by the vendor with a self contained package of execs. One of these is called to start the function. The problem is that the package is often delivered in an SMP/E target library. This library varies from release to release and may require running different versions at different times, Putting this package in either SYSPROC or SYSEXEC for public usage is both a short and long term management problem. Examples are RACF, SMP/E, IPCS, and others.
The simplest solution is to create an 'init exec' whose name is fixed and can be placed in the installation-wide exec library. The code in the iniit routine can be edited to support varying product levels. It also concatenates the specific verstion libraries under SYSPROC or SYSEXEC as appropriate for daily use. On Wed, Sep 29, 2021 at 3:06 PM Skip Robinson <jo.skip.robin...@gmail.com> wrote: > 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 <charl...@mcn.org> wrote: > >> That's why we get the big bucks. >> >> Charles >> >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of Paul Gilmartin >> Sent: Wednesday, September 29, 2021 11:01 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
