Re: Age of model 810 (was: disk cache batteries)

["Jim Franz" <franz400@xxxxxxxxxxxx>]

my mistake on the age - i do think some model was upgraded into the current
810.
This company came off a mainframe into iSeries about 3 - 4 years ago.
Hopefully this is not the normal cache battery life?
jim
----- Original Message ----- 
From: "Al Barsa" <barsa@xxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Sunday, April 17, 2005 6:33 PM
Subject: Age of model 810 (was: disk cache batteries)


>
> The model 810 was first announced in early 2003.
>
> 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
>                                        disk cache batteries
>              04/17/2005 06:29
>              PM
>
>
>              Please respond to
>              Midrange Systems
>                  Technical
>                 Discussion
>              <midrange-l@midra
>                  nge.com>
>
>
>
>
>
>
> We finally got thru our fix of disk cache batteries (iSeries 810 only
> perhaps 4 years old).
> The only clue we had was that the system became extremely slow during a
> conversion test, running about 3 times slower. The CE claimed it shouldn't
> have hit us that hard. I think otherwise - we were running large cpylib,
> many chgpf's of big files, and adding 7 gig of files w/RPG to existing 10
> gig.
> Manager asking if I can prove it was the batteries (this was our final
test
> before go-live).
> Can anyone else confirm losing cache batteries could cause such an effect?
>
> btw- our only clue of hardware problem was wrkdsksts & F11 screen showed
> disks in "degraded" status. After an ipl, we did get following 2 msgs in
> qsysopr queue:
> * *Attention*  Contact your hardware service provider now.
> Message ID . . . . . . :   CPPEA12       Severity . . . . . . . :   99
> A critical system hardware problem has occurred. Critical Message Handler
>     has been run.
> Message ID . . . . . . :   CPP8988       Severity . . . . . . . :   90
>
> jim franz
> --
> 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.
>