Funny, I was just looking into using dynamic I/O on our box. See http://publibz.boulder.ibm.com/epubs/pdf/hcsg1b20.pdf, Part 2 Using Dynamic I/O Configuration.
In our case we won't use it. We are memory constrained at times, and don't need the aggravation of performance problems caused by the extra memory demands of dynamic I/O. Peter -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: July 19, 2007 14:37 To: LINUX-390@VM.MARIST.EDU Subject: Dynamic I/O I've done a couple of disk changes recently that require updates to our IOCDS config, and it's getting hard to schedule a Power On Reset each time to recognize the changes. I see a checkmark on the HMC that indicates Dynamic I/O is possible if you have the right pieces in the config you import. Is anyone using Dynamic I/O, or can you point me to some docs (or perhaps another list) on this? Also, any docs on the format of the IODEVICE (and other) statemtents in this config would also be useful. Thanks, -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 ---------------------------------------------------------------------- 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. ---------------------------------------------------------------------- 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
