that contained a catalog during the life of the last IPL, read on: We had to 'rename' UCBs by deleting and readding them as a different number, no changes to the contents of the volume on the UCB address. Unfortunately we ended up in an installation wide unplanned outage because CATALOG does not support HCD dynamic activate for catalog volumes. CATALOG address space kept abending on the validly freemained UCB address forcing an IPL, even on systems where that catalog was definitely not opened again.
To add insult to injury, the catalog people completely failed to properly analyze the dumps and instead insisted that a ptf we didn't have on were our problem (and there will always be a ptf that's not on). When I demanded verification for this and an explanation that tied the (validly) freed UCB pointer to the apar, I got a lot of vague stuff and finally the good old OCO excuse of why they cannot tell us why that ptf is our problem. I started raising hell at that point, not accepting CATALOGs excuses, and catalog finally (sort of) admitted that they don't handle HCD dynamic activate. SEV1 apar OA18898 was then opened and closed SUGGESTION quite fast. The last conference call confirmed that there is absolutely no IBM commitment to fix this other than this SUG apar and some wishi washi wordings that I don't trust after this performance. (And SUG is no commitment at all.) If you have to 'rename' a UCB that ever contained a catalog, better plan for an IPL anyway! (Or do what the comment section will tell you at some point in the future once it gets changed. What's in it now is insufficient to prevent the problem.) In addition, if you get vague answers or the broad 'you're missing x number of ptfs' or the OCO excuse from CATALOG, be very wary and take that to mean that IBM doesn't have a clue what your problem is and just tries to make you go away. Did I mention that we are currently in the same situation with a different problem, but also with VSAM? This time we got the 'missing ptf' excuse despite the fact that the ptf clearly did not apply to us. No contingency plan on IBMs part if installing the ptf doesn't help, and of course the problem occured again with the missing ptf installed. The outcome of this is still undetermined, and it is only a production IMS that is affected.... Barbara Nitz ps: direct flames against IBM! -- "Ein Herz für Kinder" - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht! ---------------------------------------------------------------------- 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
