Of course; that's why you do the heavy lifting under the covers. But you need to deal with the nits so they don't have to.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Skip Robinson [jo.skip.robin...@gmail.com] Sent: Thursday, September 30, 2021 3:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I vs. JCL 90% of execs are run by general users 90% of the time, either explicitly from 'command line' or implicitly from an ISPF panel. Some of these folks may be more or less exec savvy, but most just want an exec to perform some business task with minimal fuss. They don't know or want to know how the sausage is made. Just add a touch of mustard and move on. My job as a sysprog is to install exec updates as transparently as possible with little fanfare. Users are capable of adapting to change, but they have other issues to deal with. Let's be kind to them. On Wed, Sep 29, 2021 at 4:42 PM Seymour J Metz <sme...@gmu.edu> wrote: > No: > > If you know that the procedure being run is a CLIST, you can code > the CLIST operand. If you know that the procedure being run is a > REXX exec, you can code the EXEC operand. If you do not code the > CLIST or EXEC operand on the EXEC command, the EXEC command > processor examines line 1 of the procedure for the characters > "REXX" within a comment. (The characters "REXX" can be in > uppercase, lowercase, or mixed-case.) This is known as the REXX > exec identifier. If the EXEC command finds the REXX exec > identifier, the EXEC command runs the procedure as a REXX exec. > Otherwise, it runs the procedure as a CLIST. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf > of Skip Robinson [jo.skip.robin...@gmail.com] > Sent: Wednesday, September 29, 2021 1:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: PL/I vs. JCL > > Is that operand required? > > On Wed, Sep 29, 2021 at 10:12 AM Seymour J Metz <sme...@gmu.edu> wrote: > > > By directly, do you mean explicit use of EXEC? There's an operand to > > distinguish CLIST from REXX. > > > > > > > > -- > > Shmuel (Seymour J.) Metz > > http://mason.gmu.edu/~smetz3 > > > > > > ________________________________________ > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > > of Skip Robinson <jo.skip.robin...@gmail.com> > > Sent: Wednesday, September 29, 2021 12:42 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: PL/I vs. JCL > > > > How about invoking a module directly? No SYSPROC is involved here. > > > > EX 'dsn(member)' > > > > I have no way to test it at the moment. > > > > On Wed, Sep 29, 2021 at 7:22 AM Seymour J Metz <sme...@gmu.edu> wrote: > > > > > TSO SYSPROC is the only case I know of where /* REXX */ is required. > > > > > > > > > -- > > > Shmuel (Seymour J.) Metz > > > http://mason.gmu.edu/~smetz3 > > > > > > ________________________________________ > > > From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on > behalf > > > of Phil Smith III [li...@akphs.com] > > > Sent: Wednesday, September 29, 2021 10:06 AM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Re: PL/I vs. JCL > > > > > > Bob Bridges wrote: > > > > > > >Purely by the way, but I've never really understood why so many REXX > > > modules I see start like this: > > > > > > > /* REXX */ > > > > > > <snip> > > > > > > > > > > > > I think (a) it's documented that way in some places; (b) Some > > environments > > > may even require that; (c) that's how some/many examples have it; and > (d) > > > it's bizarre, because these all work in TSO: > > > > > > /* Rexx */ > > > /* This rexx program. */ > > > > > > /* This is (rexx) */ > > > > > > /* This is not(rexx)s */ > > > > > > /* Thisisrexxyep */ > > > > > > but > > > > > > /* This is a program */ > > > > > > does not. So something is parsing the entire first line, looking for > the > > > leading "/*" and four letters "rexx" in a row, case-insensitive. > Bizarre. > > > > > > > > > > > > Having grown up in VM, I'd never even thought about it, other than > > knowing > > > that I needed the word "rexx" in the first line in TSO. (On VM, just > the > > > leading "/*" is sufficient.) > > > > > > -- > > > > Skip Robinson > > 323-715-0595 > > > > > -- > > -- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
