Re: UPS handling

[Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>]

If your UPS are the good network managed kind you can get a program that
talks to them and therefore gets the real remaining battery time from them.
based on that you can then shutdown whatever you want.
You may combine the serial alert with the network one or use them for
everything. Of course, when down to restricted state you can't have
anything so i don't know if there is a way to override the QUPSDLYTIM... or
maybe have a program that when going down to restricted sets the time and
when starting subsystems it sets it back to *nolimit?
I also have 90+ UPS (only 1 but still...) and i end up shutting down
everything manually...

On Fri, Apr 24, 2015 at 12:22 PM, <rob@xxxxxxxxx> wrote:

> I plan on using QUPSDLYTIM and QUPSMSGQ to do some sort of clean shutdown.
>
> Our UPS lasts a really long time, like 90 minutes or more.
>
> I thought of using *NOMAX for QUPSDLYTIM but I have an issue with that.
> One, if you brought your system down to restricted state and then the
> power failure hits it kills the system right then and there if the message
> queue specified in QUPSMSGQ is not locked by a job.
> Two, if the shutdown program 'hangs' then your system does no orderly
> shutdown.
>
> But if I make that value too small then my program may not be done anyway.
>  But with 90+ minutes I can make it pretty substantial.
>
> Any thoughts on this?
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.