Esteemed gurus:
We are a basic sysplex running z/os and z/os.e 1.4 on a z890-350. We shifted most all of our work to z/os.e about a month ago and have observed no ill effects. But we are seeing a slow loss of ESQA on the z/os.e LPAR. The SHOWZOS tool shows thousands of 'owner gone' entries. About half showing 112 bytes, the other 224 bytes. All that I can see are batch jobs. Again, there is nothing like this on the z/os LPAR. The jobs do not seem to have anything in common. Of the 3,800, there are seven jobs that are unusual (only 32 bytes) include RMM reports, DB2 image copies, and DFDSS backup jobs. There are about two dozen entries that have more then 224 bytes. I used TASID to view ESQA storage. I saw a few AQAT eye catchers, but mostly hex zeros. The only common denominator I suspect so far is OW57231 and our job scheduler. The job scheduler is a 'slave' or 'proxy' for the 'master' running on the z/os LPAR. I have a query in to that vendor. Does this ring any bells with anyone? Any suggestions on how to isolate the offending code? Anything to be added to my top ten suspects list? Is there an RMF report that might be helpful? Thanks!! ---------------------------------------------------------------------- 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
