RE: Disk failure monitoring

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>]

Is there any chance that your system failed to call home for some
reason?   

We were not plagued with the multiple disk failures that some
experienced a few years back and the two times we have had a disk
failure the system called home by itself and the CE called back right
away, but to be fair the second level text of the *Attention* message
does say "Press F14 and report the problem."

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Wed, 8 Jun 2005 08:47:22 -0500
from: rob@xxxxxxxxx
subject: Disk failure monitoring

First of all, I didn't get a phone call from IBM when the following
occurred in QSYSOPR, so I'm kind of torqued about that:
* *Attention*  Contact your hardware service provider.
* *Attention*  Contact your hardware service provider.
  A critical system hardware problem has occurred. Critical Message
Handler
    has been run. 
* *Attention*  Contact your hardware service provider now. 
  A critical system hardware problem has occurred. Critical Message
Handler
    has been run. 
  Unit   38 with device parity protection not fully operational.
  Unit   40 with device parity protection not fully operational.
  Unit   41 with device parity protection not fully operational.
  Unit   42 with device parity protection not fully operational.
  Unit   46 with device parity protection not fully operational.
  Unit   47 with device parity protection not fully operational.
  Unit   48 with device parity protection not fully operational.
  Unit   51 with device parity protection not fully operational.
  Unit   52 with device parity protection not fully operational.
  One or more device parity protected units still not fully operational.
  One or more device parity protected units still not fully operational.

(every hour after that)
...

But what notification should happen, and how would it be best for us to
get notified when STRSST 1. Start a service tool 1. Product activity log
1. Analyze log Starts peeling off these:
System                                  Resource      Resource
Ref Code     Date      Time      Class  Name          Type 
B6005120     06/07/05  08:55:31  Info   CMB01         2844 
B6005120     06/07/05  08:55:31  Info   DD040         4327 
B6005120     06/07/05  08:55:31  Info   CMB01         2844 
B6005120     06/07/05  08:55:32  Info   CMB01         2844 
B6005120     06/07/05  08:55:38  Info   DD040         4327 
4327FFFE     06/07/05  09:04:43  Pred   DD040         4327 

Near as I can tell these started at midnight the morning of Tuesday June
7.

Message ID . . . . . . :   CPPEA03       Severity . . . . . . . :   99  
Message type . . . . . :   Information  
Date sent  . . . . . . :   06/07/05      Time sent  . . . . . . :
00:02:40
  
Message . . . . :   *Attention*  Contact your hardware service provider.

Cause . . . . . :   Internal analysis of exception data indicates that  
  hardware service is recommended to maintain system availability.  
Recovery  . . . :   It is recommended that you contact your hardware 
service
  provider to have failing item 53P3360 serviced, failure to do so could
  result in a loss of system availability.  
    Press F14 and report the problem.  
Technical description . . . . . . . . :   LIC Predictive Analysis  


Rob Berendt
--
Group Dekko Services, LLC