RE: Power Handling program?

Let's break this down into two parts:

Part 1
<snip>
...When it receives the queue entry from the partition connected to the
UPS...
</snip>
Actually all partitions, IBM i and otherwise are connected to the UPS.

Part 2
<snip>
...(the program setup to watch QUPSMSGQ)...
</snip>
However, if you only have one lpar of IBM i who cares about QUPSMSGQ
that's another story. The others can be running fat dumb and happy with a
huge QUPSDLYTIM and rely upon this lpar to handle it all.
That's one way of doing things. I think I prefer each to handle QUPSMSGQ.
Why?
- multithreading. While one lpar is shutting down stuff, especially if
there are delays and stuff built in, the other lpars can be doing their
own shutdowns.
- redundancy. Let's say you have your lpar with QUPSMSGQ in it doing some
restricted state operation or undergoing maintenance at the time of power
outage (Murphy can be a real SOB). Granted, the odds of you being
snuggled in bed with visions of sugar plums dancing in your head while you
have an lpar down are a little low but as a fellow with multiple lpars I
have been known to go to a child's sporting event while a less critical
lpar was doing a full system save and rclstg.

That, and any lpar of VIOS and AIX is going to get that UPS signal anyway.

I do like Jim's idea of communicating to the HMC directly from IBM i. But
how do you put that delay in so you can get the lpar down and then the HMC
can shutdown the firmware?

Rob Berendt