|
Apparently this is a bug !!..... To do with the date 19/2/99 ?, IBM have said that this has effected 2000 + users. Not sure exactly of the facts on this one, as I was travelling and have not spoke to IBM in detail. Ours happened on a S40, V4R2 at 0601, and then went fully op by 0604 ??. If I find anything out will post here. Thanks Nick Nick Arnold Production Services Manager, IBM Certified Specialist, Certified Novell Administrator. -----Original Message----- From: WCORK@groendyke.com <WCORK@groendyke.com> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Date: 19 February 1999 18:53 Subject: RE: Unit XX With Device Parity Protection not operational? >I had the same messages this morning the error message was CPI1161. > >I talked to me CE and there was a PTF out there for this. The PTF for V4R2 >is MF19794. > >MF19794: Report fail disk units when no failure accrued. > >Wayne >System Administrator >Groendyke Transport Inc. >wcork@groendyke.com > >> -----Original Message----- >> From: Steve Roach [SMTP:sroach@manus.com] >> Sent: Friday, February 19, 1999 10:46 AM >> To: 'Midrange Mailing List' >> Subject: Unit XX With Device Parity Protection not operational? >> >> Hello: >> >> This morning, our AS/400 popped up a series of messages that looked like >> this: >> >> Unit 25 with device parity protection not fully operational. >> >> This message was repeated for units 25, 26, 27 and 28. Afterwards, >> another >> message popped up that stated: >> >> Units with device parity protection fully operational. >> >> Does anyone have any idea what the "units" are? Are they disk drives? It >> has me a little worried since our UPS failed and we have been without one >> for several weeks, now. We are still waiting for a new one. We are using >> an S30 model running V4R2. >> >> I would appreciate any information. >> >> Thank you, >> >> Steve Roach >> Vestcom/Manus Direct, Seattle >> (206)325-2200 x 245 >> >> >> +--- >> | This is the Midrange System Mailing List! >> | To submit a new message, send your mail to MIDRANGE-L@midrange.com. >> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >> | To unsubscribe from this list send email to >> MIDRANGE-L-UNSUB@midrange.com. >> | Questions should be directed to the list owner/operator: >> david@midrange.com >> +--- >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.