Being a few miles away from the datacenter and relying on telephone conversations with frazzled operators, they may not have understood what I wanted when I asked them to vary the ICC CHPIDs off from the systems.
You are correct. When the first LPAR brought the ICC CHPIDs online to it, the card reset and everything came back online and access was restored. ----------------- Judson West Teradata, a division of NCR Corporation -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, August 29, 2006 4:46 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: ICC Problems On Tuesday, 08/29/2006 at 02:47 MST, Judson West <[EMAIL PROTECTED]> wrote: > To ?reset? or ?reload? the ICC, you have to vary off the CHPIDs to the ICC from > ALL LPAR?s. We were not doing this since the holdout LPAR was a new one and > since there was no console for it, it was just ignored. Taking the CHPIDs > offline at the HMC is not effective. Once they came offline then back on, the > ICC responded as expected. Just so's you know: That's the same for all OSAs, ICC or otherwise. But your statement about the vary off on the HMC not working doesn't jive with what I've been told and have experienced. If you vary the chpid off to all LPARs (whether via HMC or commands in each LPAR), the OSA should reset. My experience has also been that the reset doesn't occur until you VARY it online to the first LPAR. THEN it reboots, presumably to allow stand-alone card diagnostics. (Though it has been a while since I played with it.) Alan Altmark z/VM Development IBM Endicott
