Re: Comments in SYS1.PARMLIB

[Cheryl Watson]

Hi all,

There is actually a Health Check for Parmlib called ICE, but it's developed and 
marketed by NewEra Software.  See http://www.newera-info.com.  They have 
wonderful products, and their customers rave about them.  If you're not 
familiar with their website, check it out for a lot of free information and 
webinars, with an emphasis on security and auditing.

Cheryl

Cheryl Watson
Watson & Walker, Inc.
www.watsonwalker.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of R.S.
Sent: Wednesday, August 24, 2016 2:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

IMHO there should be a Health Check for whole parmlib, that means all members 
from Tuning Ref.


-- 
Radoslaw Skorupka
Lodz, Poland

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

Re: Comments in SYS1.PARMLIB

[R.S.]

W dniu 2016-08-24 o 15:11, Elardus Engelbrecht pisze:

Charles Mills wrote:


Plus, are there not third-party PARMLIB syntax checkers which would have been 
broken by the change?

There are some syntax checkers from IBM, but only for *certain* parmlib members:

CEEPRMxx, LOADxx and GRSRNLXX checked by 'Parmlib Processing tool' and 
'Symbolic Parmlib Parser'

IKJTSOxx by TSO PARMLIB CHECK(??)

BPXPRMxx you use 'SETOMVS SYNTAXCHECK'

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



IMHO there should be a Health Check for whole parmlib, that means all 
members from Tuning Ref.



--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.


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

Re: Comments in SYS1.PARMLIB

[Jesse 1 Robinson]

For years my fiercest hot button has been not structural syntax differences 
among components but the scurrilous practice of introducing a keyword change in 
one release that is incompatible with the previous release(s). Over the years 
we've seen this with various products/components. SMS (PDSE-related keywords) 
and Netview (INITRTN in SSN) come to mind. Such incompatible members cannot be 
shared among different releases and complicate both forward migration and 
(godforbid) fallback. It's been a while since one of these bricks has fallen on 
us, so it appears that IBM's internal politicking has worked. 

In one grand instance, Peter Relson was able to promote a major change in one 
key member, IEASYSxx. A new keyword WARNUND in IEASYSxx does this: if an 
undefined keyword is encountered, issue a warning message but continue the IPL. 
It applies only to the contents of IEASYSxx, and it's incumbent on the sysprog 
to verify that it's really a new keyword and not merely an old one misspelled. 
If other products/components introduced such support, our lives would be 
improved. WARNUND for SMS would have saved us a lot of grief moving to z/OS 
1.6. And back several times! It would not have helped in the Netview case, 
where one release required INITRTN while the previous release could not 
tolerate it. Still, it's the right direction for all products/components. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elardus Engelbrecht
Sent: Wednesday, August 24, 2016 6:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Comments in SYS1.PARMLIB

Charles Mills wrote:

>Plus, are there not third-party PARMLIB syntax checkers which would have been 
>broken by the change?

There are some syntax checkers from IBM, but only for *certain* parmlib members:

CEEPRMxx, LOADxx and GRSRNLXX checked by 'Parmlib Processing tool' and 
'Symbolic Parmlib Parser'

IKJTSOxx by TSO PARMLIB CHECK(??) 

BPXPRMxx you use 'SETOMVS SYNTAXCHECK'

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

Re: Comments in SYS1.PARMLIB

[Elardus Engelbrecht]

Charles Mills wrote:

>Plus, are there not third-party PARMLIB syntax checkers which would have been 
>broken by the change?

There are some syntax checkers from IBM, but only for *certain* parmlib members:

CEEPRMxx, LOADxx and GRSRNLXX checked by 'Parmlib Processing tool' and 
'Symbolic Parmlib Parser'

IKJTSOxx by TSO PARMLIB CHECK(??) 

BPXPRMxx you use 'SETOMVS SYNTAXCHECK'

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

Re: Comments in SYS1.PARMLIB

[Charles Mills]

The inconsistent PARMLIB syntax horse escaped from the barn many years ago.

I am not an IBM "insider" but it is obvious to me that re-engineering every one 
of the PARMLIB consumers to support a uniform (and marvelous) syntax, while 
maintaining backward compatibility, would have been a Sisyphean task.

Plus, are there not third-party PARMLIB syntax checkers which would have been 
broken by the change?

I'm not a sysprog. When I need a PARMLIB change I send an e-mail with please 
and thank you. But I think IBM deserves thanks for what they have done, even 
though it admittedly falls way short of perfect.

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Edward Gould
Sent: Tuesday, August 23, 2016 10:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Cheryl:


> On Aug 23, 2016, at 2:51 PM, Cheryl Watson <che...@watsonwalker.com> wrote:
> 
> Hi Ed,
> 
> Regarding "Letting IBM off with variations is nonsense.", I choose to think 
> of it as being pragmatic.  I can complain all day about how IBM's reduction 
> of staff is hurting the mainframe, but the fact is that they are doing it 
> despite anything I might say or do.  Believe me that putting people to work 
> on implementing "/" and "*/" in each parmlib member is NOT going to make it 
> into the line items for a new release with higher priority work and reduced 
> staff size.  

I believe in holding IBM to a standard that they themselves developed. I 
shudder to think that each parmlib member will have it own syntax. This goes 
agains every thing that IBM espouses. I will be long gone and I still think 
that this will be a dangerous precedent. As I said in my previous email, I have 
had to do updates to parmlib on the fly as a fellow sysprog forgot a comma and 
all of a sudden VTAM would not come up nor CICS due to an APF issue because of 
a stupid missing comma.  Luckily I never made the mistake.  

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

Re: Comments in SYS1.PARMLIB

[Peter Relson]

>This was one of our big SHARE requirements and we worked hard at it. 
>You should be able to put comments in any SYS1.PARMLIB member now.  If 
>you find a member that's not supported, please let us know.

I would not have said that the thrust was necessarily about 
"any...member". Support for many members were added.
There certainly was no general direction with respect to "any" (but 
perhaps the list from the Share team addressed "most" of those that did 
not meet their needs). I would expect any new member to support /*...*/ 
comments.

FWIW, the Share req was in some cases not about "comments at all" but 
about "comments not necessarily at the bottom of the member or at the end 
of a line".

>For example, you can nest comments as follows: 

It is very likely that many of the cases that support /*...*/ comments do 
not support "nesting" of comments. And if they don't, they won't. 
At the point in the documentation shown by Cheryl, it should be "looser" 
(as in "might").

I see from Skip Robinson's post that IEASYMxx is one such member. I don't 
know when/how/where the general commentary about "nested" that Cheryl 
pasted got put in. I suspect that one of the parsers used by some parmlib 
members handles that case. Many (I suspect most) do not.

>Wouldn't that resource (and the customers') have been more productively
>spent in making the syntax uniform? 

No it would not have been. There is about perhaps 100 or 1000 to 1 
difference in "resource" needed in order to accomplish "uniformity" (let 
alone dealing with the unacceptable incompatibilities that would result). 

Peter Relson
z/OS Core Technology Design


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

Re: Comments in SYS1.PARMLIB

[Edward Gould]

Cheryl:


> On Aug 23, 2016, at 2:51 PM, Cheryl Watson  wrote:
> 
> Hi Ed,
> 
> Regarding "Letting IBM off with variations is nonsense.", I choose to think 
> of it as being pragmatic.  I can complain all day about how IBM's reduction 
> of staff is hurting the mainframe, but the fact is that they are doing it 
> despite anything I might say or do.  Believe me that putting people to work 
> on implementing "/" and "*/" in each parmlib member is NOT going to make it 
> into the line items for a new release with higher priority work and reduced 
> staff size.  

I believe in holding IBM to a standard that they themselves developed. I 
shudder to think that each parmlib member will have it own syntax. This goes 
agains every thing that IBM espouses. I will be long gone and I still think 
that this will be a dangerous precedent. As I said in my previous email, I have 
had to do updates to parmlib on the fly as a fellow sysprog forgot a comma and 
all of a sudden VTAM would not come up nor CICS due to an APF issue because of 
a stupid missing comma.  Luckily I never made the mistake.  
> 
> Before I wrote up the requirements, I did a thorough study of the Parmlib 
> members and found that about half allow '*' in the first position.  Because 
> different departments work on each Parmlib member, I had to write up a 
> separate requirement for each one, and it would have taken years (if ever) to 
> get them all changed.  Then Peter Relson, who wears many hats and is trusted 
> by everyone in IBM, offered to do all the coding if he could implement the 
> '*' version because, obviously, it's the least amount of coding (if a = '*' 
> then bypass).  I said that it would meet my requirements, the MVSE 
> Requirements committee agreed, and he had it done a week later.  If we had 
> forced IBM to do it the "right way", it wouldn't be done today.  At least now 
> there is an option to put comments in the Parmlib members that didn't have 
> them.
Then write a requirement that *ALL* parmlib members must use the same syntax. 
That allows IBM to come up with one standard. It shouldn't be up to the users 
to fight over syntax on each member. I have seen (and IBM agreed to) several 
global requirements (like the syntax for parmlib idea) that IBM agreed to and 
with a two GUIDE meetings it was accepted. The problem is I don’t remember 
which one it was (its been 20+ years) :(

> 
> And as my first email suggested, I think it would make a lot of sense for 
> people to add a comment box at the top of every Parmlib member that includes 
> not only an example of comments, but provides a place to put comments.  You 
> can save newbies a lot of trouble (and down time) in the future.  

Sorry I don’t buy off on that. Besides a *LOT* of people just copy what comes 
in the servpac now days. It dangerous to accept that people are going to read 
comments first. That is why IBM doc is pretty much world class (until OMVS came 
along that is)
> 
> I think this is just one of many compromises that we'll need to make with a 
> reduced IBM staff, but I'd rather work within the system and get some things 
> accomplished.  (I could only wish our political parties could do the same.)  
> ;-)

Documentation (good) is an IBM mainstay. Changing the rules for each member 
will let the CA’s of the world do their own thing and we will be left with no 
standards. 

> 
> All my best,
> Cheryl
Standardization is a good thing as it allow sysprogs to update every member the 
same way. Changing the standard (such as it is) is just asking for a 
catastrophe.


> 
> SNIP---

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

Re: Comments in SYS1.PARMLIB

[Charles Mills]

Perfect is the enemy of good.

(Attributed to Voltaire, Confucius and others.)

Charles

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

Hi Ed,

Regarding "Letting IBM off with variations is nonsense.", I choose to think of 
it as being pragmatic.  I can complain all day about how IBM's reduction of 
staff is hurting the mainframe, but the fact is that they are doing it despite 
anything I might say or do.  Believe me that putting people to work on 
implementing "/" and "*/" in each parmlib member is NOT going to make it into 
the line items for a new release with higher priority work and reduced staff 
size.  

Before I wrote up the requirements, I did a thorough study of the Parmlib 
members and found that about half allow '*' in the first position.  Because 
different departments work on each Parmlib member, I had to write up a separate 
requirement for each one, and it would have taken years (if ever) to get them 
all changed.  Then Peter Relson, who wears many hats and is trusted by everyone 
in IBM, offered to do all the coding if he could implement the '*' version 
because, obviously, it's the least amount of coding (if a = '*' then bypass).  
I said that it would meet my requirements, the MVSE Requirements committee 
agreed, and he had it done a week later.  If we had forced IBM to do it the 
"right way", it wouldn't be done today.  At least now there is an option to put 
comments in the Parmlib members that didn't have them.

And as my first email suggested, I think it would make a lot of sense for 
people to add a comment box at the top of every Parmlib member that includes 
not only an example of comments, but provides a place to put comments.  You can 
save newbies a lot of trouble (and down time) in the future.  

I think this is just one of many compromises that we'll need to make with a 
reduced IBM staff, but I'd rather work within the system and get some things 
accomplished.  (I could only wish our political parties could do the same.)  ;-)

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

Re: Comments in SYS1.PARMLIB

[Cheryl Watson]

Hi Ed,

Regarding "Letting IBM off with variations is nonsense.", I choose to think of 
it as being pragmatic.  I can complain all day about how IBM's reduction of 
staff is hurting the mainframe, but the fact is that they are doing it despite 
anything I might say or do.  Believe me that putting people to work on 
implementing "/" and "*/" in each parmlib member is NOT going to make it into 
the line items for a new release with higher priority work and reduced staff 
size.  

Before I wrote up the requirements, I did a thorough study of the Parmlib 
members and found that about half allow '*' in the first position.  Because 
different departments work on each Parmlib member, I had to write up a separate 
requirement for each one, and it would have taken years (if ever) to get them 
all changed.  Then Peter Relson, who wears many hats and is trusted by everyone 
in IBM, offered to do all the coding if he could implement the '*' version 
because, obviously, it's the least amount of coding (if a = '*' then bypass).  
I said that it would meet my requirements, the MVSE Requirements committee 
agreed, and he had it done a week later.  If we had forced IBM to do it the 
"right way", it wouldn't be done today.  At least now there is an option to put 
comments in the Parmlib members that didn't have them.

And as my first email suggested, I think it would make a lot of sense for 
people to add a comment box at the top of every Parmlib member that includes 
not only an example of comments, but provides a place to put comments.  You can 
save newbies a lot of trouble (and down time) in the future.  

I think this is just one of many compromises that we'll need to make with a 
reduced IBM staff, but I'd rather work within the system and get some things 
accomplished.  (I could only wish our political parties could do the same.)  ;-)

All my best,
Cheryl

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Edward Gould
Sent: Tuesday, August 23, 2016 3:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Cheryl:

Thanks for all your work on this.
However it occurs to me that IBM is still not living up to the spirit of the 
request.
I would suggest that the “/*" and the “*/”  standard (since day one mind you) 
IS the gold standard.
Letting IBM off with variations is nonsense.
The first “GROUP” who really went off the reservation (with documentation and 
other IBM standards) was the OMVS Group.
Letting IBM set this kind of “standard” is dangerous IMO. More than one time I 
have had to make on the fly updates to Parmlib so that the IPL could be 
corrected and restarted loosing 30+ minutes (assuming I was present) in one 
case two hours. Just because of a finger check. This allowing IBM to change the 
rules for each member is IMO short sighted and will land more pressure down the 
road to standardize things… Bad decision on IBM’s part in both cases, IMO.

Ed
 
> On Aug 23, 2016, at 9:02 AM, Cheryl Watson <che...@watsonwalker.com> wrote:
> 
> Hi all,
> 
> It's true that not all Parmlib members support the same format, but 
> the Init & Tuning Guide has been updated to show which type of 
> comments are allowed in each member.
> 
> In 2011, I created a dozen SHARE requirements to add comments to the 
> remaining Parmlib members that didn't support them.  Peter Relson was 
> kind enough to come to our aid and implemented comments for the then 
> active Parmlib members.  This excerpt comes from our Tuning Letter 2013 No. 3:
> ===
> Comments
> 
> Change documentation is very dear to my heart, so I have been upset 
> for years by the fact that you could not add comments to many of the 
> parmlib members. I got so frustrated that I wrote up SHARE 
> requirements for many of the members to either add or modify the ability to 
> add comments.
> 
> Thanks to z/OS guru Peter Relson of IBM, who works with the SHARE MVSE 
> requirements committee, we now have an APAR, OA38328 (z/OS 1.12-1.13, 
> 17Apr2013, New Function - Parmlib Comment Support), that address many 
> of these requirements. The following parmlib members have been 
> modified to allow an asterisk in position 1 of a line to indicate that 
> the rest of the line is a comment:
> 
> COMMNDxx - Commands to be issued at IPL GTFPARM (or the parmlib member 
> identified by the GTF procedure) - Parameters used by the Generalized 
> Trace Facility
> IEAABD00 - Specifies data to be dumped to SYSABEND
> IEACMD00 - IBM-supplied commands to be issued at IPL
> IEADMP00 - Specifies data to be dumped to SYSUDUMP
> IEADMR00 - Specifies data to be dumped to SYSMDUMP IEAPAKxx - Link 
> Pack Area (LPA) pack list IEASYSxx - System parameter list LPALSTxx - 
> Link Pack Area (LPA) library list VATLSTxx - 

Re: Comments in SYS1.PARMLIB

[Edward Gould]

=
> 
> I hope this help,
> Cheryl
> 
> Cheryl Watson
> Watson & Walker, Inc.
> www.watsonwalker.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Feller, Paul
> Sent: Tuesday, August 23, 2016 9:43 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
> 
> I thought there was a push by IBM to allow comments in all members.  I
> thought the last few members that could not have comments now allow
> comments.  As an example I know the COMMNDxx member did not allow comments,
> but now it does.  I know the way you put in comments does vary from member
> to member.
> 
> Thanks..
> 
> Paul Feller
> AGT Mainframe Technical Support
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Tuesday, August 23, 2016 08:26
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
> 
> This is because there is no SYS1.PARMLIB owner and interpreter. Each member
> has its own owner with its own syntax rules and syntax interpreter. I
> presume it is (also here) impossible to have all the labs agree on one set
> of rules.
> 
> Kees.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Dyck, Lionel B. (TRA)
> Sent: 23 August, 2016 15:13
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
> 
> Sadly no
> 
> 
> ------
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI
> Service Delivery & Engineering
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Richards, Robert B.
> Sent: Tuesday, August 23, 2016 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Comments in SYS1.PARMLIB
> 
> 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?
> 
> z/OS' 2.1 and 2.2 installed.
> 
> Bob
> 
> --
> 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 information, services and offers, please visit our web site:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIFAg=9
> g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=jxny6Y
> sC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7UvpDSerOhMKCx2pvUh9G
> 1aPoOvE= . This e-mail and any attachment may contain confidential and
> privileged material intended for the addressee only. If you are not the
> addressee, you are notified that no part of the e-mail or any attachment may
> be disclosed, copied or distributed, and that any other action related to
> this e-mail or attachment is strictly prohibited, and may be unlawful. If
> you have received this e-mail by error, please notify the sender immediately
> by return e-mail, and delete this message. 
> 
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> 
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> 
>   
> 
> --
> 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
> 
> (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

Re: Comments in SYS1.PARMLIB

[J R]

Use the REXX approach. Start with a comment that signals that the new standard 
syntax is being used. 
/* CARDINAL SYNTAX */

Sent from my iPhone

> On Aug 23, 2016, at 12:08, Mike Schwab  wrote:
> 
> But how would you switch over to the new syntax?
> 
> On Tue, Aug 23, 2016 at 10:44 AM, Paul Gilmartin
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>> On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:
>>> 
>>> It's true that not all Parmlib members support the same format, but the Init
>>> & Tuning Guide has been updated to show which type of comments are allowed
>>> in each member.
>> Wouldn't that resource (and the customers') have been more productively
>> spent in making the syntax uniform?  Use Utilities commands as a model.
>> 
>> -- gil
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> 
> 
> -- 
> Mike A Schwab, Springfield IL USA

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

Re: Comments in SYS1.PARMLIB

[Ed Jaffe]

On 8/23/2016 8:44 AM, Paul Gilmartin wrote:

Wouldn't that resource (and the customers') have been more productively
spent in making the syntax uniform?  Use Utilities commands as a model.


Not according to IBM. It was this or nothing.

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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

Re: Comments in SYS1.PARMLIB

[Tom Conley]

On 8/23/2016 11:44 AM, Paul Gilmartin wrote:

On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:


It's true that not all Parmlib members support the same format, but the Init
& Tuning Guide has been updated to show which type of comments are allowed
in each member.


Wouldn't that resource (and the customers') have been more productively
spent in making the syntax uniform?  Use Utilities commands as a model.

-- gil

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



No, because the changes to NIP code would have been prohibitive.

Regards,
Tom Conley

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

Re: Comments in SYS1.PARMLIB

[Mike Schwab]

But how would you switch over to the new syntax?

On Tue, Aug 23, 2016 at 10:44 AM, Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:
>>
>>It's true that not all Parmlib members support the same format, but the Init
>>& Tuning Guide has been updated to show which type of comments are allowed
>>in each member.
>>
> Wouldn't that resource (and the customers') have been more productively
> spent in making the syntax uniform?  Use Utilities commands as a model.
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Comments in SYS1.PARMLIB

[Ed Jaffe]

On 8/23/2016 7:01 AM, Tom Conley wrote:


This was one of our big SHARE requirements and we worked hard at it. 
You should be able to put comments in any SYS1.PARMLIB member now.  If 
you find a member that's not supported, please let us know.


What he said!

Also, if your company is a SHARE member, please, Please, PLEASE don't 
open an RFE and then beg your "friends" through this list and other 
social media channels to click LIKE on it. [Sheesh!] It simply doesn't work.


Use the SHARE requirements system and get real results. 
http://www.share.org/page/requirements-&-advocacy


--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

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

Re: Comments in SYS1.PARMLIB

[Jesse 1 Robinson]

One additional gotcha for IEASYMxx. Guess how I learned this. An entire sysplex 
would not IPL. From KC:

"Do not use nested comments in this parmlib member."

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Cheryl Watson
Sent: Tuesday, August 23, 2016 7: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

Re: Comments in SYS1.PARMLIB

[Paul Gilmartin]

On Tue, 23 Aug 2016 10:02:30 -0400, Cheryl Watson wrote:
>
>It's true that not all Parmlib members support the same format, but the Init
>& Tuning Guide has been updated to show which type of comments are allowed
>in each member.
> 
Wouldn't that resource (and the customers') have been more productively
spent in making the syntax uniform?  Use Utilities commands as a model.

-- gil

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

Re: [EXTERNAL] Re: Comments in SYS1.PARMLIB

[Richards, Robert B.]

Thanks to all for your participation in this thread, but specials kudos to 
Cheryl Watson and Tom Conley for their efforts.

Bob

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: Tuesday, August 23, 2016 10:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [EXTERNAL] Re: Comments in SYS1.PARMLIB

THANK YOU - this is great information.

--
Lionel B. Dyck (TRA Contractor)
Mainframe Systems Programmer
Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI 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

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

Re: [EXTERNAL] Re: Comments in SYS1.PARMLIB

[Dyck, Lionel B. (TRA)]

THANK YOU - this is great information.

--
Lionel B. Dyck (TRA Contractor)
Mainframe Systems Programmer 
Enterprise Infrastructure Support (Station 200) (005OP6.3.10)
VA OI 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

Re: Comments in SYS1.PARMLIB

[Cheryl Watson]

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

Re: Comments in SYS1.PARMLIB

[Elardus Engelbrecht]

Cheryl Watson wrote:

>I just LOVE this APAR! 

No comments... ;-)

Sorry, Cheryl, but I really *love* your post. Please continue with your nice 
posts.

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

Re: Comments in SYS1.PARMLIB

[Cheryl Watson]

Hi all,

It's true that not all Parmlib members support the same format, but the Init
& Tuning Guide has been updated to show which type of comments are allowed
in each member.

In 2011, I created a dozen SHARE requirements to add comments to the
remaining Parmlib members that didn't support them.  Peter Relson was kind
enough to come to our aid and implemented comments for the then active
Parmlib members.  This excerpt comes from our Tuning Letter 2013 No. 3:
===
Comments

Change documentation is very dear to my heart, so I have been upset for
years by the fact that you could not add comments to many of the parmlib
members. I got so frustrated that I wrote up SHARE requirements for many of
the members to either add or modify the ability to add comments.

Thanks to z/OS guru Peter Relson of IBM, who works with the SHARE MVSE
requirements committee, we now have an APAR, OA38328 (z/OS 1.12-1.13,
17Apr2013, New Function - Parmlib Comment Support), that address many of
these requirements. The following parmlib members have been modified to
allow an asterisk in position 1 of a line to indicate that the rest of the
line is a comment:

COMMNDxx - Commands to be issued at IPL
GTFPARM (or the parmlib member identified by the GTF procedure) - Parameters
used by the Generalized Trace Facility
IEAABD00 - Specifies data to be dumped to SYSABEND
IEACMD00 - IBM-supplied commands to be issued at IPL
IEADMP00 - Specifies data to be dumped to SYSUDUMP
IEADMR00 - Specifies data to be dumped to SYSMDUMP
IEAPAKxx - Link Pack Area (LPA) pack list
IEASYSxx - System parameter list
LPALSTxx - Link Pack Area (LPA) library list
VATLSTxx - Volume attribute list

I just LOVE this APAR! Because you might start adding comments after the PTF
is applied, you should probably determine a standard method of documentation
that everyone can follow. This would normally include the date and time,
description of the change (including the reason for the change), and the
person making the change. You should also make a note of any dependencies
(i.e. a change in one parameter in this parmlib requires a change in another
parameter in another parmlib). Figure 3 is an example of a "flower box" (as
we used to call them) that we would insert at the beginning of every parmlib
member.  (Note - in Word, but not email, the right hand asterisks are in
line.)

Figure 3 - Documenting a Parmlib Member
**
* Notes:
*
* If you change parameter xxx, then you  *
*   should make a corresponding change   *
*   in member xx.*
**
**
* Change Log:*
* 2012/03/20, 10:30am - CLW - Changed    *
*  to  to add PROGB1 suffix  *
* 2012/03/27, 8am - CLW - Added x  per   *
*  memo from  dated 3/25/12  *
**
**

Unfortunately, you can't use the same comment box in all parmlib members,
because comments aren't always indicated in the same way. The IEASYMxx
member only allows comments when enclosed within the bounds of a /* and an
*/; TSOKEY00 only allows comments at the end of all parameters; and members
IGDSMSxx, IPCSPRxx, and IVTPRM00 don't allow any comments.

RECOMMENDATION: Apply the PTF and start adding comments to these
long-neglected parmlib members.
=

I hope this help,
Cheryl

Cheryl Watson
Watson & Walker, Inc.
www.watsonwalker.com


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

I thought there was a push by IBM to allow comments in all members.  I
thought the last few members that could not have comments now allow
comments.  As an example I know the COMMNDxx member did not allow comments,
but now it does.  I know the way you put in comments does vary from member
to member.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Vernooij, Kees (ITOPT1) - KLM
Sent: Tuesday, August 23, 2016 08:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

This is because there is no SYS1.PARMLIB owner and interpreter. Each member
has its own owner with its own syntax rules and syntax interpreter. I
presume it is (also here) impossible to have all the labs agree on one set
of rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Dyck, Lionel B. (TRA)
Sent: 23 August, 2016 

Re: Comments in SYS1.PARMLIB

[Tom Conley]

On 8/23/2016 9:10 AM, 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?

z/OS' 2.1 and 2.2 installed.

Bob



This was one of our big SHARE requirements and we worked hard at it. 
You should be able to put comments in any SYS1.PARMLIB member now.  If 
you find a member that's not supported, please let us know.


Regards,
Tom Conley

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

Re: Comments in SYS1.PARMLIB

[Nims,Alva John (Al)]

Remember the OLD picture of a "Tree Swing Designed by Committee!"

Al Nims
Systems Admin/Programmer 3
UFIT
University of Florida
(352) 273-1298

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

I am sure there was / is.. but apparently standards are inconsistent other than 
what is documented member by member.

Rob Schramm

On Tue, Aug 23, 2016, 9:43 AM Feller, Paul <paul.fel...@transamerica.com>
wrote:

> I thought there was a push by IBM to allow comments in all members.  I 
> thought the last few members that could not have comments now allow 
> comments.  As an example I know the COMMNDxx member did not allow 
> comments, but now it does.  I know the way you put in comments does 
> vary from member to member.
>
> Thanks..
>
> Paul Feller
> AGT Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Tuesday, August 23, 2016 08:26
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> This is because there is no SYS1.PARMLIB owner and interpreter. Each 
> member has its own owner with its own syntax rules and syntax interpreter.
> I presume it is (also here) impossible to have all the labs agree on 
> one set of rules.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Dyck, Lionel B. (TRA)
> Sent: 23 August, 2016 15:13
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> Sadly no
>
>
> --
> 
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10) VA OI 
> Service Delivery & Engineering
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Richards, Robert B.
> Sent: Tuesday, August 23, 2016 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Comments in SYS1.PARMLIB
>
> 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?
>
> z/OS' 2.1 and 2.2 installed.
>
> Bob
>
> --
> 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 information, services and offers, please visit our web site:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIF
> Ag=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45N
> yOc=jxny6YsC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7Uv
> pDSerOhMKCx2pvUh9G1aPoOvE= . This e-mail and any attachment may 
> contain confidential and privileged material intended for the 
> addressee only. If you are not the addressee, you are notified that no 
> part of the e-mail or any attachment may be disclosed, copied or 
> distributed, and that any other action related to this e-mail or 
> attachment is strictly prohibited, and may be unlawful. If you have 
> received this e-mail by error, please notify the sender immediately by 
> return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or 
> its employees shall not be liable for the incorrect or incomplete 
> transmission of this e-mail or any attachments, nor responsible for any delay 
> in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal 
> Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with 
> registered number 33014286
> 
>
>
> --
> 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
>
-- 

Re: Comments in SYS1.PARMLIB

[Rob Schramm]

I am sure there was / is.. but apparently standards are inconsistent other
than what is documented member by member.

Rob Schramm

On Tue, Aug 23, 2016, 9:43 AM Feller, Paul <paul.fel...@transamerica.com>
wrote:

> I thought there was a push by IBM to allow comments in all members.  I
> thought the last few members that could not have comments now allow
> comments.  As an example I know the COMMNDxx member did not allow comments,
> but now it does.  I know the way you put in comments does vary from member
> to member.
>
> Thanks..
>
> Paul Feller
> AGT Mainframe Technical Support
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Vernooij, Kees (ITOPT1) - KLM
> Sent: Tuesday, August 23, 2016 08:26
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> This is because there is no SYS1.PARMLIB owner and interpreter. Each
> member has its own owner with its own syntax rules and syntax interpreter.
> I presume it is (also here) impossible to have all the labs agree on one
> set of rules.
>
> Kees.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Dyck, Lionel B. (TRA)
> Sent: 23 August, 2016 15:13
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Comments in SYS1.PARMLIB
>
> Sadly no
>
>
> --
> Lionel B. Dyck (TRA Contractor)
> Mainframe Systems Programmer
> Enterprise Infrastructure Support (Station 200) (005OP6.3.10)
> VA OI Service Delivery & Engineering
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Richards, Robert B.
> Sent: Tuesday, August 23, 2016 8:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [EXTERNAL] Comments in SYS1.PARMLIB
>
> 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?
>
> z/OS' 2.1 and 2.2 installed.
>
> Bob
>
> --
> 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 information, services and offers, please visit our web site:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=jxny6YsC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7UvpDSerOhMKCx2pvUh9G1aPoOvE=
> . This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately by
> return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> 
>
>
> --
> 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
>
-- 

Rob Schramm

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

Re: Comments in SYS1.PARMLIB

[Feller, Paul]

I thought there was a push by IBM to allow comments in all members.  I thought 
the last few members that could not have comments now allow comments.  As an 
example I know the COMMNDxx member did not allow comments, but now it does.  I 
know the way you put in comments does vary from member to member.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Tuesday, August 23, 2016 08:26
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

This is because there is no SYS1.PARMLIB owner and interpreter. Each member has 
its own owner with its own syntax rules and syntax interpreter. I presume it is 
(also here) impossible to have all the labs agree on one set of rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: 23 August, 2016 15:13
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Sadly no


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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, August 23, 2016 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Comments in SYS1.PARMLIB

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?

z/OS' 2.1 and 2.2 installed.

Bob

--
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 information, services and offers, please visit our web site: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.com=DQIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=jxny6YsC6RioMY8630Lu5CRHRmeQTyBBluARUP3_NGI=LHCFuRbZpRcIsVd7UvpDSerOhMKCx2pvUh9G1aPoOvE=
 . This e-mail and any attachment may contain confidential and privileged 
material intended for the addressee only. If you are not the addressee, you are 
notified that no part of the e-mail or any attachment may be disclosed, copied 
or distributed, and that any other action related to this e-mail or attachment 
is strictly prohibited, and may be unlawful. If you have received this e-mail 
by error, please notify the sender immediately by return e-mail, and delete 
this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



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

Re: Comments in SYS1.PARMLIB

[Elardus Engelbrecht]

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

Re: Comments in SYS1.PARMLIB

[Vernooij, Kees (ITOPT1) - KLM]

This is because there is no SYS1.PARMLIB owner and interpreter. Each member has 
its own owner with its own syntax rules and syntax interpreter. I presume it is 
(also here) impossible to have all the labs agree on one set of rules.

Kees.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (TRA)
Sent: 23 August, 2016 15:13
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Comments in SYS1.PARMLIB

Sadly no


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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, August 23, 2016 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Comments in SYS1.PARMLIB

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?

z/OS' 2.1 and 2.2 installed.

Bob

--
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 information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286



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

Re: Comments in SYS1.PARMLIB

[Dyck, Lionel B. (TRA)]

Sadly no


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

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Tuesday, August 23, 2016 8:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Comments in SYS1.PARMLIB

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?

z/OS' 2.1 and 2.2 installed.

Bob

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

Comments in SYS1.PARMLIB

[Richards, Robert B.]

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?

z/OS' 2.1 and 2.2 installed.

Bob

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