Peter, raise a hardware incident with IBM as soon as you can - if the DS8k hasn't already called home and raised one. The refcode allows IBM to identify a failing FRU and is not documented for customer use as far as I know.
As you have messages for two device numbers so the commonality is likely to be some shared component within the DS8k that is *not* volume-related. Given that it is labelled as a serious alert, I wouldn't delay. Do you have any form of Metro Mirror implemented? Are you hyperswap-capable? On Wed, 11 Dec 2024 at 09:15, Peter < [email protected]> wrote: > Hello > > > I am looking for manual to explain me the meaning of the ref code . > > Does anyone have any references for the below reference code ? > > > IEA480E 6234,DASD,SERIOUS ALERT,MT=2107,SER=0175-HGC91, 152 > > REFCODE=BE32-0203-0009,VOLSER=/UNKN/,ID=01,SENSE=00901B40 003CCF01 > > 8F804002 03000904 E508FF0B 0000BE32 05100200 FE000000 > > *IEA480E 601C,DASD,SERIOUS ALERT,MT=2107,SER=0175-HGC91, 153 > > REFCODE=BE32-0203-0009,VOLSER=/UNKN/,ID=01,SENSE=00901B40 003CCF01 > > 8F804002 03000904 E508FF0B 0000BE32 05100200 FE000000 > > > > Peter > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
