Be careful with how you define the MAXDEVS. It will have an effect on
your ability to do dynamic IO gen changes. I agree that the HSA has
gotten a lot bigger than it was. IBM's answer is it has to be bigger to
support all the new stuff.
Paul Feller
AIT Mainframe Technical Support
[EMAIL PRO
I kept the LPARs but I really cut down on the OSA adapters.
We have 4 OSA cards.
2 that supports the ICC devices
2 that supports are normal network traffic
When I defined all the addresses and then gave all addresses to all 4 lpars.
Now, all the addresses on the DS6800 are on all LPARs, but I a
Did you cut back your HSA by removing LPARs, reducing MAXDEVS, or both?
Mostly I want to verify that MAXDEVS impacts HSA size.
Brian Nielsen
On Wed, 16 Aug 2006 15:33:43 -0500, Tom Duerbusch
<[EMAIL PROTECTED]> wrote:
>I do believe that it is the max devices defined, but that is also across
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 dependen
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 LPAR
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
i
On Tue, 15 Aug 2006 08:28:47 -0600, Lee Stewart
<[EMAIL PROTECTED]> wrote:
>This reminds me of my first week or so working for IBM as a PSR (those
>were kind of software CEs for those of you too young to know). I was
>working in Dayton, OH and they sent me out to Wright Patterson air base
>to pic
It turned out that my problem was the way my application was built.
I had started with a main routine using the CMS Multitasking applmain( )
linkage. I thought I needed to use applmain( ) to use the multitasking
functions. The main routine created a thread which initially did not have any
TCP
