We are booting rootvg from external SSA.
It works nicely. The only issue is that the SSA drives do not always keep the same "hdisk" number.
This is most evident when you are performing something like a migration upgrade/install. When booting from the CDROM, the names of the individual SSA drives are likely to change. The CDROM boot process numbers the disks the way it sees them, not the way the system saw them when you last built it.
Before booting on CDROM or from any other media, record the Serial number of the pdisk in addition to it's hdisk and pdisk numbers. IBM has a Service Aid under the TASKS option from a maintenance boot and diagnostics that allows you to relate the physical serial number of the SSA pdisk to a logical hdisk name.
Once you have this relationship discovered during your Maintenance IPL, you can then choose which drive(s) your rootvg resides on and procede with your upgrade.
Remember that the SSA drives are named/numbered in order of the physical serial numbers of each drive (These are visible on the drives as well). So, in the course of day to day operations, you encounter an opportunity to replace a pdisk, you introduce new serial numbers into the SSA loop. During normal boots, this is ok, as the ODM remembers the relationships of these drives to the PDISKs. I think that this is acutally based on PVIDS. I have had to learn not to depend on hdisk numbers, or PDISK numbers for that matter, and depend on PVIDS and Physical Serial Numbers.
Having this HDISK, PDISK, PVID and Phyiscal Serial Number relationship documented somewhere other than on the system can prove to be a lifesaver, or at least a system saver.
I have seen folks try to perform a migration install on their datavgs instead of rootvgs and panic when the migration install process indicated that no rootvg was found on the physical volume selected for the migration install. They even started to re-install from a mksysb,
risking all their userdata.
Again, normal day to day operations do not present this opportunity, its the booting from CDROM or tape that consistently presents this scenario.
IBM has recently announced support for rootvg IPLs from external SSA. Make sure to update your bootlist and document the PVIDS and Physical Serial numbers of the rootvg hard drives.