A quick search on ‘comment’ does not show such a requirement.

René

> On 29 Sep 2021, at 16:02, Seymour J Metz <sme...@gmu.edu> wrote:
> 
> Does the ANSI standard require the first line to be a comment?
> 
> 
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> 
> ________________________________________
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of 
> Tony Thigpen [t...@vse2pdf.com]
> Sent: Wednesday, September 29, 2021 9:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: PL/I vs. JCL
> 
> Also of note, z/VM REXX requires that the first thing in a ReEXX program
> *must* be a comment. It does not require the word REXX, just a comment.
> "/* */" is seen a lot.
> 
> z/VSE REXX does not require that the first thing be a comment, but
> suggests that the first thing be a comment starting with "/* REXX ....
> */ for compatibility, but it does not state who requires it for
> compatibility.
> 
> Tony Thigpen
> 
> CM Poncelet wrote on 9/28/21 9:58 PM:
>> The "/* REXX */" part is required only if the REXX exec is to be run
>> from a PDS allocated to DDNAME=SYSPROC instead of to DDNAME=SYSEXEC.
>> 
>> SYSPROC is for CLISTs, SYSEXEC is for REXXs.
>> 
>> 
>> 
>>> On 29/09/2021 02:07, Andrew Rowley wrote:
>>> On 29/09/2021 6:54 am, Bob Bridges wrote:
>>>> Purely by the way, but I've never really understood why so many REXX
>>>> modules I see start like this:
>>>> 
>>>>    /* REXX */
>>>>    /* Module: Name
>>>>       Author: Bob Bridges the Magnificent
>>>>       Purpose: Convert ANSI dates to internal format, or whatever. */
>>>> 
>>>> ...instead of something like this:
>>>> 
>>>>    /* This REXX converts ANSI dates to internal format, or whatever. */
>>>>    /* Module: Name
>>>>       Author: Bob Bridges the Magnificent */
>>> 
>>> I guess the first looks like a statement with a purpose, the second
>>> looks like a comment that can be freely edited e.g.
>>> 
>>> /* This program converts...
>>> 
>>> Things may not be as obvious to newcomers as they are to those with
>>> more experience.
>>> 
>> 
>> ----------------------------------------------------------------------
>> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to