THANK YOU - this is great information.

--------------------------------------------------------------------------
Lionel B. Dyck (TRA Contractor)
Mainframe Systems Programmer 
Enterprise Infrastructure Support (Station 200) (005OP6.3.10)
VA OI&T Service Delivery & Engineering


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Cheryl Watson
Sent: Tuesday, August 23, 2016 9:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Comments in SYS1.PARMLIB

Hi all,

Most of the problems have been in the older members, but it's been getting 
better since IBM included this section in the Init & Tuning Guide.  (ISVs 
should be aware of these guidelines too.):
==================================================
General syntax rules for the creation of members

The following general syntax rules apply to the creation of most parmlib 
members. You can find the description of the exceptions to these rules under 
specific members. The general rules are:

-- Logical record size is 80 bytes.
-- Block size must be a multiple of 80.
-- Any columns between 1 and 71 can contain data.
-- Statements are entered in uppercase characters.
-- Suffix member identifiers can be any combination of A-Z and 0-9, though some 
member identifiers may allow other characters.
-- Columns 72 through 80 are ignored.
-- For some parmlib members, continuation is indicated by a comma followed by 
one or more blanks after the last entry on a record.
-- Leading blanks are suppressed. A record therefore need not start at a 
particular column.
-- Suffix member identifiers (such as LNK=A2) can be any alphanumeric 
combination.
-- Comments for some parmlib members are indicated by using /* and */ as the 
delimiters in columns 1-71, for example:
/*comment*/
/* and */
characters within a single-quoted string are usually not treated as comment 
delimiters. For nested comments, delimiters must be balanced. For example, you 
can nest comments as follows:
/*comment1/*comment2*/*/
Some parmlib members require other methods. Check specific parmlib members for 
information about specifying comments.

============================================

Cheers!
Cheryl

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Tuesday, August 23, 2016 9:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Richards, Robert B. wrote:

>This has probably been asked before, but a quick search of the archives did 
>not yield the results I was looking for.

>Do all members of SYS1.PARMLIB now support /*  */  commenting?

No. There is only one standard with this name: 'NO STANDARDS'   ;-)


IEASYSxx has this:
DIAG=00,                      COMMENT

ARCCMDxx:
/* COMMENT */
SETSYS ...

ADYSETxx:

* COMMENT
  DAE ...

Oh, not all members have the same set of continuation syntax. 

Some members have this:

 STATEMENT KEYWORD,

Others like ARCCMDxx has this:

SETSYS -
  NODEBUG

I could go on...

Good luck trying to untangle this...

Groete / Greetings
Elardus Engelbrecht

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

(null)

----------------------------------------------------------------------
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