On Mon, 11 Feb 2013 02:50:14 -0500, Jim Mulder wrote: >IBM Mainframe Discussion List <[email protected]> wrote on >02/11/2013 02:09:58 AM: > >> From: "nitz" >> To: [email protected], >> Date: 02/11/2013 02:17 AM >> >> "The CEA TSO/E address space manager can create up to 10 concurrent >> address spaces for a single user, and can create a maximum of 50 >> concurrent TSO/E address spaces. You can use the same processes >> that you use to work with other TSO/E address spaces when working >> with the TSO/E address spaces that are created by the CEA TSO/E >> address space manager." >> >> I would like to know what imposes this limit and if there are plans >> to lift it. > > I think those are arbitrary limits, for the purpose of >preventing an errant program or user from using too many >address spaces, and also for allocating the storage for >the table which is used to keep track of these address >spaces. Do you have a scenario where these limits would be >too low for your installation's intended use of this >function? > Does this count address spaces started by syscall fork() when OMVS runs under TSO?
Does it count adress spaces started by USS Rexx "address TSO"? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
