You have to activate HyperPAV usage via the IECIOSxx Parmlib member
(HyperPAV=Yes). The LSSes used by this LPAR will be converted to HyperPAV
LSS.
Sysplex 1 will have HyperPAV=No, and will continue to operate as before. Any
LSS that has been converted to HyperPAV usage (by Sysplex 2) will be no
longer have Alias addresses bound to Base addresses.
With your current setup : Sysplex 1 - Dynamic Alias management and Sysplex
2 - Static management, Sysplex 1 is always dictating what the Alias/Base
relationship for Sysplex 2 will be. Most likely this is not what you
originally wanted. Much worse would be if Sysplex 2 also managed the Aliases
dynamically!
Sysplex 2 will move de aliasses in the "Hyperpav way" and sysplex 1 will
move
the aliasses the "WLM way"
HyperPAV aliases don't have a long term base assignment, so it is wrong to
think of them as being moved around since they are only assigned for the
duration of an I/O.
Once the LSS is converted, WLM can't manage the Alias/Base assignement since
there is now an unbound pool of HyperPAV Aliases. Sharing LCUs like this is
not a good idea.
John
Anyone some experience with activating HyperPav in an environtment with 2
sysplexes shareing some LCU's (both sysplexes dynamic PAV) ?
Would like to start/activate hyperpav in one sysplex with no impact to the
other sysplex.
Today's situation is like this :
Sysplex 1 useing LCU xx HCD/IODF configuration WLMPAV=Yes
Sysplex 2 useing LCU xx HCD/IODF configuration WLMPAV=NO
Doeing this , sysplex 1 is moves the aliasses , the "WLM way".
Sysplex 2 will not move the aliasses.
But what will happen when hyperpav is activated on sysplex 2.
I was told that WLMPAV=YES/NO is of no influence in a hyperpav
environment.
Sysplex 2 will move de aliasses in the "Hyperpav way" and sysplex 1 will
move
the aliasses the "WLM way" .
Will this work ?
----------------------------------------------------------------------
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
