Peter, I agree that I wished I can rely on the fact that when a (enforced, syntactical) limit is not documented, means there is no limit. Apparently I can expect this from IBM.
Not in every time this is clear and one might wonder how the absence should be interpreted. For this I like the MICF documentation that always states the range of the value of a variable, even when: "RANGE OF VALUE: PAGAPF ranges from a minimum of 0 to a maximum that is limited only by practical bounds." Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Peter Relson > Sent: 03 February, 2017 19:13 > To: [email protected] > Subject: Re: COUPLExx syntax question > > >I think it would be useful to document this absence of practical > limitations. > > What you are really talking about is not the absence of a practical > limitation but the absence of any enforced or expected limit. There is > (always) a practical limit. That limit is whatever would cause "too > much" > resource to be used. That's not to say that that practical limit is > necessarily anywhere near the typical in-practice usage. > > I do not agree with your thought. When there is an enforced limit, I > expect it to be documented. It is not feasible to document the lack of > enforced limit for everything. Perhaps you can explain why it would be > more important to document the fact that there is no enforced limit for > this one thing than for the other tens of thousands of no-enforced limit > things. > > You should expect, in the absence of a statement that there is no > enforced > limit, that indeed there is no enforced limit. All enforced limits > should > be documented; it could well be that the doc falls short there, and we > would appreciate learning of such shortcomings. There is always a > practical limit. The hope is that the practical limit exceeds the > in-practice usage. > > 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 ******************************************************** 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 [email protected] with the message: INFO IBM-MAIN
