It was an OS problem after all, and not due to the MCLs. APAR OA29370 has been opened.
We have been over the 65535 device boundry for a long time, but the bug became exposed when I deleted over 5000 addresses the week before via dynamic iogen activate. The PAV assignment code broke because of the 2 byte CMCTHMBI field. We have just been lucky for several years that the truncated value (to fit the field) resulted in a value that was higher than our highest UCB. With the recent deletion of the 5000+ devices along with the truncation, we ended up with a total number of devices being tracked that is less than our starting DASD UCB. Strange though that the propblem didn't actually start until the next weekend when we performed a power-on-reset. Still investigating that one... Dave ---------------------------------------------------------------------- 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
