As other collegues mentioned,there are many reasons you may see these messages.If there is FICON Director and these are shared by any device that you have touched its connection,it makes sense. An IFCC error can cause "inoperative path" to connections that you did not do any change even. You might have checked these already but better to mention : 1-Any device in this conenction or sharing these connections have the minimum microcode level installed or not - SPAR guide and exception letter from resourcelink 2-Checking which channels you got IFCC error from HMC as well.IBM can understand details from this information. 3-Having HW CE do a function test to cards.
Better is have HW CE check error messages and get help from IBM and DWDM provider both as SW and HW. There is one command with path that IBM did as "FICON RAS enhancement" that shows more in detail reasons of inoperative path ( D M=DEV(XXXX,(ch)) ) where XXXX device number ch is channel number. This shows RNID information Check for IOS2001I and IOS2002I and and RNID information .Related APAR is OA13644,OA10906 Just to share experience:( Better is always get help from HW and SW support,because cases can be different and working on troubleshotting of IOS related messages are sometimes dangerous ) Sometimes even all microcode levels are ok,cards are ok (if HW CEs did a function test on cards on z10 and DWDM and everything seems working fine) you may see inoperative path messages after this kind of work. Then posibble cause can be FICON cables plug/unplug without making paths offline to devices from z/OS which can cause IFCCs to occur in any shared paths. This type of case MAY be solved by offline/online physicall channel.If these are channels that you can do offline/online : >From all Operating systems, offline all paths,channels (SW offline) then >Using HMC,online these channels (HW online) and from z/OS online channels and >paths.They will become online as soon as you do HW online,but as far as I >remember,SW online makes some difference. Regards Meral -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ibm Main Sent: Monday, May 30, 2011 1:17 PM To: [email protected] Subject: Re: [IBM-MAIN] INOPERATIVE PATH Hi, thanks for your anwsers. The "inoperative path" appeared in devices (3490) tha are physsicaly at our other site. Both sites are connected through a DWDM network with FICON cascading. Lizette: The affected CHPIDs are 06 and 96, have a closer look at the IOS450E. The "DS P,xxxx" shows that the path through 06 and 96 the are inoperative (<). The "D M=CHP(06)" shows that the paths are not operational ($). We have checked close to every hardware component (fibers, SFPs,...) involved in the path to the CU, and everything seems to be working OK. My question was why can paths get inoperative without a meaningful infrastructural change. We upgrade one z10 to z196, but the IOS appeared in LPARs in the "old" z10, where nothing was changed. Thanks in advance. Regards, Christian. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This message and attachments are confidential and intended solely for the individual(s) stated in this message. If you received this message although you are not the addressee, you are responsible to keep the message confidential. The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments. Our company shall have no liability for any changes or late receiving, loss of integrity and confidentiality, viruses and any damages caused in anyway to your computer system. Bu mesaj ve ekleri, mesajda gonderildigi belirtilen kisi/kisilere ozeldir ve gizlidir. Bu mesajin muhatabi olmamaniza ragmen tarafiniza ulasmis olmasi halinde mesaj iceriginin gizliligi ve bu gizlilik yukumlulugune uyulmasi zorunlulugu tarafiniz icin de soz konusudur. Mesaj ve eklerinde yer alan bilgilerin dogrulugu ve guncelligi konusunda gonderenin ya da sirketimizin herhangi bir sorumlulugu bulunmamaktadir. Sirketimiz mesajin ve bilgilerinin size degisiklige ugrayarak veya gec ulasmasindan, butunlugunun ve gizliliginin korunamamasindan, virus icermesinden ve bilgisayar sisteminize verebilecegi herhangi bir zarardan sorumlu tutulamaz. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
