I used REXX in OS/2, but can't remember if it had any special
requirements for the first line. I can't find any manuals online (yet).
Tony Thigpen
Seymour J Metz wrote on 9/29/21 10:22 AM:
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.)
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
