That is really huge (768K, that is). I remember a 64K HSA on our 3081. It could grow in increments of 64K. And the location was dynamic - if a storage error was encountered when loading the HSA during POR, it would drop down to the next lower segment. The amount of storage it needed was dependent on the configuration; the lowest address it took was influenced by the quality of the memory.
In the modern era, our HSA does take 2G. There are several LPARS and we have thousands of devices. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] > Behalf Of Tom Duerbusch > Sent: Wednesday, August 16, 2006 1:34 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: HSA size question > > > I do believe that it is the max devices defined, but that is > also across > LPARs. > > What initially bit me, was I defined 4 lpars. Why? I don't know. I > needed two, a 390 and an IFL. But I thought about a test one and > perhaps a "systems" one. And the convention was to define the devices > to all LPARs. Well, almost 2 GB for HSA convinced me otherwise. Even > if I didn't bring up the LPAR, the definitions took their > pound of HSA, > hence real storage. > > I cut things back to the minimum of 768M HSA size. > > I remember when OS/VS 2 took 768K for the superviser. Is the HSA > process 1,000 times more complex then OS/VS 2? > > Tom Duerbusch > THD Consulting > > >>> [EMAIL PROTECTED] 8/16/2006 2:32 PM >>> > On a z/890, does the size of the HSA change if the value of > the MAXDEVS > > parameter on the RESOURCE statement in the IOCP is > increased/decreased? > > The z/890 System Oveview manuals says the HSA size varies according to > > the "size and complexity of the I/O configuration", but it's not clear > if > it refers to the actual defined devices or the maximum > devices that can > be > defined. It makes the most sense for it to be the maximum > devices, but > > I'd like to verify it. > > Brian Nielsen >
