Please bear with me, normally I don't do CA stuff! - When I tested standalone dump a while back (fortunately on our sysprog sandplex), we noticed that some jobs stayed locked in CA11 and consistently receive abendu0999 until the (corrupted?) CA11 database is somehow cleared.
My colleague (who has *a lot* more patience than I do) has run out of patience by now with the "support" we got for this problem from CA. There was even a guy here from CA, and they still don't appear to have any idea what's going on. Did I mention that the problem is easily reproducible? All it takes is two lpars running MUF (we call it AD11STRT) in a sysplex. One of those systems gets silenced by either sadump or (like this morning) by just doing a load for the lpar without any orderly shutdown. MUF comes up without any problem, but some jobs (in our case those that are running periodically like dcollect) afterwards get the abend consistently (until some sort of repair is run on the database). We cannot tell which jobs will be affected beforehand, and they were NOT running when the system died. The messages are always (twice) U11-011 U11PDS REQUEST SERVICE ERROR; REQ:08 SVCRET:00 SVCREAS:00 CRQECB:40000000 CRQRC:0010 and then with different reason codes U11-011 U11PDS REQUEST SERVICE ERROR; REQ:10 SVCRET:08 SVCREAS:38 CRQECB:40000064 CRQRC:0010 CA had given us a slip trap which (of course) didn't hit because the message is not "U11-011" but rather " U11-011", and the end was in the wrong position, too. Never believe a slip trap you're given! Has anyone else seen this? By making it public, I am also hoping that someone from CA will take an interest in this who knows what he is doing. Thanks and regards, Barbara Nitz ---------------------------------------------------------------------- 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
