Re: ups messages and loss of power

Hi, everyone:

In case anyone wants to look at that "sample code" that Al mentioned ... the
"book" that Al referred to is the earlier edition(s) of the OS/400 Backup
and Recovery Guide ... Apparently, in the V4 timeframe, as Al mentioned, IBM
started to pull material out of some of the printed manuals (to "save a
tree" and cost) and then put (some of) it into the "InfoCenter" on-line ...

But, there is some "good news" -- you can still find the V3R2 version of
those manuals, here:

    http://publib.boulder.ibm.com/pubs/html/as400/online/v3r2eng.htm

In this case, you want the "OS/400 Backup and Recovery -Advanced" manual,
SC41-3305-1, as that is where the sample code resides. (The "OS/400 Backup
and Recovery - Basic" manual refers you to the Advanced manual for this
topic.)

Regards,

Mark S. Waterbury

----- Original Message -----
> From: "Al Barsa" <barsa@xxxxxxxxxxxxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Saturday, June 18, 2005 7:24 PM
> Subject: Re: ups messages and loss of power
>
> The coding of this function got a lot of activity after the massive
> blackout that his the New York to Michigan areas in August 2003.  The
> system values alone are inadequate.  You need a fair amount of coding to
> pull off this function.  The sample code in the book (which is no longer
> printed) has both syntax and logic errors.  Try this tool:
>
> http://www.taatool.com/document/L_upsmon.htm
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> "i" comes before "p", "x" and "z"
> e gads
>
> Our system's had more names than Elizabeth Taylor!
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
> http://www.as400connection.com
>
>
>
>
>              "Jim Franz"
>              <franz400@xxxxxxx
>              r.com>                                                     To
>              Sent by:                  <MIDRANGE-L@xxxxxxxxxxxx>
>              midrange-l-bounce                                          cc
>              s@xxxxxxxxxxxx
>                                                                    Subject
>                                        ups messages and loss of power
>              06/18/2005 07:20
>              PM
>
>
>              Please respond to
>              Midrange Systems
>                  Technical
>                 Discussion
>              <midrange-l@midra
>                  nge.com>
>
>
>
>
>
>
> Customer had major power failure (truck hit power poles).
> We have cable connected from Best UPS to i5 (with proper cable fitting).
> We know power failed at 4am, and exactly 3 hours later the QHST log
> at 7am is last entry for a job running.
> QUPSDLYTIM is set to 3 hrs
> The UPS msgq is still default QSYSOPR.
> Since QSYSOPR is empty when machine IPL'd, is there no QHST log
> record showing loss of power? We can't find one.
> Are there specs for talking to the UPS to get remaining battery time?
> This is a lights out operation nights/weekends and I need something
> automated.
> jim franz
>
> btw - from previous post on Disaster Recovery - they were down 15 hours
for
> iSeries
> (lack of power) and another 24 hours till all of Win network came up (some
> WinServer services did
> not startup 1st time)
> --
> 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.
>
>
>
> --
> 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.
>