Thanks to all that responded. Having the feature ?enable dynamic_I/O? set in the parm does not do any good. When z/VM is reactivated, it is automatically disabled because of an invalid z/VM token. This is because I maintain the I/O configuration under z/OS and the token is z/OS. From the manual:
If one operating system discovers (by checking the configuration token) that the other operating system "owns" the I/O configuration, the operating system that discovered the change will disable its own dynamic I/O support. That is, if z/OS finds a VM configuration token in the hardware system area (HSA), z/OS disables its dynamic I/O support and, thereafter, can only make changes to the software I/O configuration. If z/VM finds a z/OS configuration token, z/VM disables its dynamic I/O support and, thereafter, can make software-only changes. I deactivated and reactivated the LPAR and that still did not do any good. I think what you meant was the ?Enable New_Devices_Initialized_When_Added?. I issued a ?q new_devices? which said it was already enabled. I queried the CHPID and it said it was online but there were no devices. However, once I varied the CHPID online, all my devices appeared. One last question: How can I query which IOCDS z/VM is using: Thanks as always. Peter Alan Altmark <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 08/19/2005 10:42 PM Please respond to Linux on 390 Port <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: z/VM I/O Config Question On Friday, 08/19/2005 at 10:03 EST, "McKown, John" <[EMAIL PROTECTED]> wrote: > > I just implemented some modifications to our I/O > > configuration using HCD > > on z/OS. We maintain our IODFs under z/OS and issue activates for the > > other z/OS LPARs. How do I get z/VM to recognize our new I/O changes > > dynamically? Thanks. > > It appears that you will need to create an IOCP input deck from the z/OS > IODF file in question and send that over to the z/VM system (to the user > which will be doing the dynamic activation - probably MAINT?) As long as DYNAMIC_I/O is enabled in SYSTEM CONFIG, CP will react to devices that come or go due to dynamic updates to the I/O subsystem. No need to send the IODF to VM since VM isn't the LPAR controlling the I/O config. (Unlike MVS, CP doesn't use an IODF to figure out what devices are available and what kind they are.) Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
