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 [[email protected]] on behalf of
Skip Robinson [[email protected]]
Sent: Wednesday, September 29, 2021 1:48 PM
To: [email protected]
Subject: Re: PL/I vs. JCL
Is that operand required?
On Wed, Sep 29, 2021 at 10:12 AM Seymour J Metz <[email protected]> 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 <[email protected]> on behalf
> of Skip Robinson <[email protected]>
> Sent: Wednesday, September 29, 2021 12:42 PM
> To: [email protected]
> 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 <[email protected]> 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 [[email protected]] on behalf
> > of Phil Smith III [[email protected]]
> > Sent: Wednesday, September 29, 2021 10:06 AM
> > To: [email protected]
> > 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 [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
