> Is "region" still a valid term or has its use been deprecated? Is it the > best term? Is "address space" better? I am thinking, for example, of > "region" in a context loosely defined as "the logical place that one job > runs in" such as "there is only one TIOT for a given region" - a sense in > which it is *roughly* equivalent to "initiator."
Region and address space are related but not the same thing. The REGION is the subset of the address space that is made available to user programs. The REGION size (endlessly debated here) is your ambit claim for how much you think the work running in the address space might GETMAIN concurrently. That number is massaged by your IEFUSI exit and the REGION limit is set. GETMAIN more than that and you get an S878 or S80A abend. You can also think of the REGION as being made up of the low private subpools. Net-net it's a subset of the address space. > Is the term equally applicable to started tasks as to batch jobs? If not, > what is the correct word for the context of a started task? All the same. > What is the equivalent term for a TSO user address space? To update the > phrase above, "there is only one TIOT for a given batch region or TSO > _____"? A TSO address space is just an address space and in general there is one TIOT per address space, but that's only because in general there is only one real job step task. If you're privileged and you attach (and set up) more concurrent job steps, then you can have more TIOTs. Their behavior is not all sweetness and light, but it's doable. > Thanks. I'm writing some documentation and wanted to use the precise term. I would say "address space" is the correct term in the context you're using it. CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
