>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 [email protected] with the message: INFO IBM-MAIN
