>...then REGIONABOVE refers to only 31-bit storage (so why NOLIMIT?) The answer basically comes down to history and compatibility.
Region (and Region=0M) existed long before there was storage above 2G, and has always referred to 31-bit storage. Compatibility dictates that it always will so refer. And "0M" always meant that there was no defined limit via that specification (which could be overridden by various exits processing). On the face of it you should expect that Region(NoLimit) means that there is no defined limit of storage that is in the Region category. And it does indeed mean that. Thus I conclude that perhaps at the crux of the matter is that you might not have understood what Region refers to in its z/OS context. 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
