Re: Removing unused 3286 from IODF

2007-01-18 Thread Johnston, Robert E
Thanks Roy and Kevin for the info. I'll put this on the back burner until I foresee some downtime coming up. Those old definitions don't bother me so much after all! :) Much appreciated, Robert Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the

Re: Removing unused 3286 from IODF

2007-01-18 Thread R.S.
Dave Kopischke wrote: [...] I think you'll still want a POR though. I don't know of any other way to remove those definitions from HSA without a POR. The room those definitions take up in HSA might not be an issue, but if you're deleting a bunch of devices, it might help you later if you find

Removing unused 3286 from IODF

2007-01-17 Thread Johnston, Robert E
Hello again... I have an old 3274 controller defined in IODF that is no longer installed. The 1st 24 addresses are defined as 3279s or 3278s and I added DYNAMIC=YES to those definitions so that I can delete them in a future IODF. The last 8 addresses are defined as 3286-2 and I can't figure out

Re: Removing unused 3286 from IODF

2007-01-17 Thread Roy Hewitt
Robert, Forget the Activate, you're gonna need an IPL!.. 3286 just don't support dynamic activate.. no way around it that I know of. (Last time I got caught out by this, I deleted a whole bunch of old 3274 entries without looking too carefully at all the OSConfigs.. then started activating

Re: Removing unused 3286 from IODF

2007-01-17 Thread Neubert, Kevin (DIS)
I'm not certain about z890/z990 and beyond, but if the device does not support dynamic capability it certainly appears a power-on reset will be necessary. Regards, Kevin -- For IBM-MAIN subscribe / signoff / archive access

Re: Removing unused 3286 from IODF

2007-01-17 Thread Roy Hewitt
Neubert, Kevin (DIS) wrote: I'm not certain about z890/z990 and beyond, but if the device does not support dynamic capability it certainly appears a power-on reset will be necessary. Kevin, A POR is not usually required, it's only the definition in the OSCONFIG that causes the problems.. so