× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Did the attention light turn on?  Of course, if this is on your 570 you
can't see it anyway because it's a light tube which terminates behind
quarter-inch thick smoked plastic.  On the 550s and 520s, you could
drive your car through fog with the attention light.  The 595's is just
plain creepy - ominous rectangular block above the giant red EPO switch.

I think the reason you saw it at midnight was because the PAL analyzer
runs a few times a day, once must be at midnight - it saw the FFFE
errors (I have a feeling if you look back in your PAL you'll see a lot
more of the FFFE's), flagged it bad, sent notice to QSYSOPR, and off you
go.

Just a theory.  These things have minds of their own on occasion,
however.

Justin C. Haase - iSeries System Administrator
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation
email - justin.haase@xxxxxxxxxxxx
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, June 08, 2005 8:47 AM
To: midrange-l@xxxxxxxxxxxx
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
Dept 01.073
PO Box 2000
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.



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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.