Mark Post: This is a follow up for you on the unanswered question of PAV volumes in the HFS but not as root volume.
In the native LPAR configuration with FICON and a switch, under which I was unable to boot a freshly installed system installed on a PAV device, I have successfully used a PAV volume as swap and as part of the file system. This demonstrates PAV access once booted is NOT a problem (as I suspected since I could install to them). I wanted you to know that the theoretical had been tested, For the list at large: I now must resolve the fact that I have the PAV devices in my HFS and as a swap volume and I'd like to change them without burning down the house. It appears that yast made my swap volume dasda, but in any case I have dasdb1 mounted at /, dasdd1 mounted at /usr and dasdc1 mounted at /var I intend to copy the /var tree to dasdb1 and unmount dasdc1. I would then like to add a swap volume using a 1 gb custom volume in the shark box. So I need to know the following: First, how do I go about changing the swap volume so that on the next IPL it uses the new swap volume and releases the old one. Secondly, how do I remove dasdc1 and dasda1 (the devices are B040 and B041) from the installed configuration so they will not be accessed on the next IPL, Third, how do I make other volumes available once I've got an installed configuration. The other complication is that the head systems programmer wants to give me a dedicated escon channel with only the devices I've been given for current and future use (a total of 8 devices, 4 - 9 gig devices and 4 - 1 gig devices) so that's going to mess things up more isn't it? Any advice in coping with this situation or would it be easier to rebuild the universe ?
