Re: Impending cache battery pack failure

Justin,

This fills in the blanks!

Pete


Haase, Justin C. wrote:

The help is inside the batteryinfo text, I was able to get it by putting
in an incorrect parm.
------------------------------------

This macro allows you to force an IOA to put its cache battery pack

into an error state. This IOA state requires replacement of the

battery. Typically, this option is performed when you are replacing a

cache battery pack on one IOA, and want to replace other cache battery

packs on IOAs in the same system which have not yet issued the cache

battery warning or cache battery error. This macro also lets you

display information about the cache battery (battery type, power on

hours, etc).





Usage: BATTERYINFO <<-INFO> <-FORCE> <-LIST>> <<-ALL> <-IOA IOANAMES>>



-INFO...: Retrieve information about a cache battery pack.

-FORCE..: Force an error on a cache battery pack.

-LIST...: List the IOA.



-ALL....: This command is performed on the cache battery packs of all

         IOAs on the system.



-IOA....: This command is performed only on the cache battery packs

         of the specified IOAs.  You may specify any number of IOAs,

         separated by spaces.

         For example: -IOA DC01 DC02 DC03



Sample usage:



   Retrieve battery information on the cache battery packs for

   DC01 and DC02:

         of the specified IOAs.  You may specify any number of IOAs,

         separated by spaces.

         For example: -IOA DC01 DC02 DC03



Sample usage:



   Retrieve battery information on the cache battery packs for

   DC01 and DC02:

   BATTERYINFO -INFO -IOA DC01 DC02



   Force the error state on the cache battery pack of all IOAs

   on the system:

   BATTERYINFO -FORCE -ALL



   List all IOA names on the system:

   BATTERYINFO -LIST




--
Justin C. Haase - iSeries System Engineer
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Monday, February 27, 2006 3:20 PM
To: Midrange Systems Technical Discussion
Subject: Re: Impending cache battery pack failure

Thanks Rob, Chad, et al on the FAQ.

Just a clarification This will be a Do it Yourself procedure so do I understand that I have to force the failure first, using SST (or DST) in

order to make sure that the change is "registered" (my term)? IOW, I
first force the failure (while in a restricted state) and THEN replace
the battery pack?

Just want to make sure.  I was just in DST but I couldn't see an option
to force the failure and the help on BATTERYINFO was non-existent.

Just hope my local Radio Shack or battery place can match the pack. Plenty of posts here about that. Didn't see a specific reference to a

model 800 (controller is a 5703) but it looks like the battery pack
isn't all that hard to match.

Thanks,

Pete

rob@xxxxxxxxx wrote:

I don't think you'll lose any data.  But performance will suffer

greatly.

One thing I have schedule to run about a week prior to scheduled downtime (have to give the CE time to order parts and schedule) is http://faq.midrange.com/data/cache/418.html

Rob Berendt

--
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.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.