Have a 1.4 system that is a totally separate/isolated environment that
doesn't share any dasd with the 1.7 systems I have on the same CEC. All
HCD work is done on the 1.7 system and a copy of the IODF is shipped
across to the 1.4 system. For some unknown reason, when the IODF V5 was
unloaded onto the 1.4 system, HCD on the 1.4 system indicates that it is
in V4 format. The hw activate was done on a 1.7 system and all the 1.7
systems are happy, but when the 1.4 system was ipl'ed, it gave the IOS505A
message indicating the hw and sw tokens are out of synch.
What I would like to do is rename the current 1.4 IODF which is in V4
format and get another copy of the V5 Format IODF from the 1.7 system and
name it the same and re-ipl the 1.4 system. I am then hoping that the
IOS505A message will no longer be issued.
So the IODF on your 1.4 system is somehow not the correct one. Your
plan is sound. Once you get the correct IODF to your 1.4 system, you
could activate it and you'd find that it is back in sync.
Tom
If he renames his existing IODF, which we assume is incorrect, and then
replaces this with an identically named correct IODF, he wont be able to
do any activates - an IPL will be required - as the replacement IODF
timestamp will not match that in the instorage (CDA) control block
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
