Another place to look if that isn't the answer is the interface
cards/chips at either end of the cable. It would be feasible for there
to be a hardware error that was not logged by the device/CU that was
cable or interface related, even if the error was occurring at that end
of the cable.  

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: The IBM z/VM Operating System 
> [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark
> Sent: Tuesday, November 04, 2008 3:06 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Interface control check
> 
> On Tuesday, 11/04/2008 at 09:31 EST, "Mrohs, Ray" 
> <[EMAIL PROTECTED]>
> wrote:
> 
> > Just looking for possible causes of a new problem. We 
> started getting 
> > interface control checks whenever Hidro or Connect:direct 
> try to start 
> > up. In both cases they are doing their own version of formatting or 
> > writing to disk. System is up and running, and regular CMS 
> formats, as 
> > well as spooling and paging all look good. The problem happens over 
> > all
> > 4 chpids and any disks behind them. IBM helped with a trace and it 
> > shows a 'real' hardware problem. Hitachi stated there are 
> no hardware 
> > errors on their end. When the problem first appeared, an unused ICF 
> > was being recharacterized as an IFL by the IBM CE (within 
> the same few minutes).
> > I'm trying to figure out why there would be a connection.
> 
> If you're getting them on all 4 chpids, then there must be 
> something common to all 4 chpids that is causing the problem:
> - Are all 4 chpids plugged into the same card on System z?
> - Is your director/switch logging any errors?
> - Did someone yank on a group of cables, damaging them or 
> stressing the connectors?
> 
> Back in the day, an IFCC on a copper channel was usually the 
> result of a bent pin or poorly seated connector.  That is, 
> electrical signals were not flowing properly.  If the light 
> isn't shining properly, you can get an IFCC on an optical 
> cable.  The h/w guys will have to help you with that.
> 
> Alan Altmark
> z/VM Development
> IBM Endicott
> 

Reply via email to