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



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.