Dave Kopischke wrote:
On Tue, 5 Jun 2007 11:28:42 +0100, Roy Hewitt wrote:
You dont even need to create the IOCDS, remember the IOCDS is only ever
used at POR time...so if PORs are hard to come by, then you can defer it
until you really need to...
If you don't create and activate a new IOCDS with the IODF, I believe you'll
get hardware/software mismatch messages at every IPL until you get them
synched up. Depending on your environment, you might have trouble finding
the matching IOCDS if you let it languish for a long time. I would suggest a
policy of keeping them synched up to avoid subsequent problems.
Dave,
I completely agree that it is a very good policy to always update an
IOCDS when you update an IODF.. you never know when you will do that
unexpected POR! But the IOCDS is only ever used at CPC POR time, and has
nothing to do with the 'sync' issue with an ACTIVATE, neither has it
anything to do with IPL processing. Both these events use information in
the currently active hardware config loaded in HSA. This might have been
loaded from an IOCDS at POR, but could also have come from a previous
ACTIVATE..
If you do POR from an out of date IOCDS, then yes, you can end up in a
mess as the automatic selection (if you are set up that way) of the IODF
will probably choose a non-synced config, and then ACTIVATES become
something of a 'struggle'..
Just to reiterate, my point was that there is no great rush to POR..
plus John should still be able write an IOCDS using one of the methods
mentioned.
Regards
Roy
----------------------------------------------------------------------
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
