Ok. Now we come down to the pro's and con's of bringing down your guestedIN theory yes but only if this changes the way the disks are presented to the 'hostee'. If that's the case seems like you'd have bigger fish to fry at that point.
partitions first. Let me toss out a couple of questions.
1 - If the IPL of the hosting partition applies some ptf's applying to
partition hosting, could negative ramifications occur?
2 - If the power down of the hosting partition also includes powering down*FATAL. Because then you've killed the guest partition. Although luckily you must initiate this intentionally. The firmware won't accept updates or restart if other partitions are running and of course our guest partition is still running here.
the whole unit to apply some non concurrent firmware could negative
3 - If you bring the hosting partition down to a restricted state and tryNot likely. Although it should be assumed if you ever restore that and then attempt to IPL the guest partition it will at the very least be an Abnormal IPL because you didn't quiesce the guest first so lots of stuff could be 'in flight'.
to save '/QFPNWSSTG' will undesirable results occur?
4 - If while the hosting partition is down you replace a cache card and/orNope. So long as the system stays running and the guest partition happily waits you'd be good.
a disk drive could negative ramifications occur? Keeping in mind that, if
done properly, then nothing negative would have been experienced on the
5 - If you bring this whole system down this way and leave it down for a*FATAL because when the entire system comes down the guest partition crashes hard.
length of time could negative ramifications occur? Perhaps long enough to
ship your system from one city to another?