John Kelly wrote:
I understand that to synch the IODF and IOCDS for more than 'software
change' that I need to
ACTIVATE IODF=A0,ACTIOCDS=A0
This should make the H/W (HSA) and S/W happy on the LPAR that I issue the
command? My question is 'will it make the other LPARs unhappy', in that
the HSA won't reflect their IODF, before an IPL or ACTIVATE in the other
LPARs?
After activation, other LPARs will be out of sync. You will need to do
software-only activation to get them back in sync.
Also will VM/Linux 'see' the changes without disruption/IPL?
You can do dynamic updates using z/VM HCD just like you can with z/OS.
Use the CBDSACT command.
Finally in MVS, the LOAD parm specifies the HCD's "operating system
configuration" but how does VM respond/accept it?
z/VM does not have a LOADxx member and IPLPARM data set. The z/VM load
parm has nothing to do with IODF processing.
Rather, in z/VM you have an IODF statement in the SYSTEM CONFIG file on
the PARMDISK used at IPL.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
