>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
