Hello list, I had the following question in July of this year. I just want add to the archive the resolution of this problem.
<Snip from July 2008> Our system is a 2096 U03 with three LPARs but no sysplex. Two LPARs are production, one at z/OS 1.4 and a small one at z/OS 1.7. The current IODF is a version 5 level. This weekend I activated a new IODF on the 1.4 system using the HCD dialogs which completed successfully. I did not do an activate on the 1.7 We then IPLed the 1.4 system and it just waited. The NIP console was not activated and there was not a hard wait. I brought up my rescue system and changed the IODF back to the old one and the 1.4 system IPLed ok. <end of snip> The problem was I had two control unit # 2 on the same path because I did not requested EMC to verify my IODF. HCD did not object because it had to do with the DMX1000 internal mapping of CHIPIDs. This obviously caused the DMX1000 to do some sort of diagnostics. My IODF error was partially due to the fact that our maintenance contract had expired with EMC and we had not completed negotiations with a third party to support the DMX1000. Regards, Listen. Think. Solve. Steve Wolf Rockwell Automation 414-382-4308 ---------------------------------------------------------------------- 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
