Kurt, The "set off" command logically removes the volume from use. It does not detach it from the guest or LPAR. So, if a "set on" command is issued for the same device number, it can be immediately re-mounted and used. This would allow you to use the device in another guest or LPAR without losing any data. But, there is a data integrity exposure if someone on the first system does a "set on" command for the device and starts using it again.
I would like to see a "remove device" command that would go one step further and require another "add device" before the volume is usable again. I'm not sure why, it just seems "right" to me. Perhaps a little bit of professional paranoia. Mark Post -----Original Message----- From: ZIEGENBEIN, Kurt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 5:18 AM To: [EMAIL PROTECTED] Subject: /proc/dasd/devices Hi! I'm searching for a complete documentation for the proc-dasd interface. I found on the IBM web-pages a short description of some comand you can send to the interface: echo "add device range=devno-range" >> /proc/dasd/devices echo "set device range=devno-range off" >> /proc/dasd/devices echo "set device range=devno-range on" >> /proc/dasd/devices add device range: works great -- it makes a device-range visible to the system set device range on,off: I havn't tried these, because i'm not sure what will happen. the documentation tells me that "This resets the state of the devices as if they had never been defined as DASD". What does this mean? I'm looking for a command that is the exact opposite to "add device range": a way to remove dome DASDs, without destroying their content. I want to use this to "give" some dasds from one LPAR to another... any hints? ciao Kurt
