On 5/9/2014 6:51 PM, CM Poncelet wrote:
So there is a "third kind" of problem when an ISV cannot fix yet will not release its code and the ISV has not 'gone bust', because its source code in escrow cannot then be accessed either.
My worst experience of this kind was the ADRDSSU CONSOLIDATE bug that corrupted certain files > 21cyls on EAV whenever a DASD fast replication copy operation failed and needed to be retried in software. Initially thinking we had a "PDSE becoming corrupt" issue, I opened up three or four related (and never solved) PMRs with IBM beginning in June 2009. It was extremely frustrating and I kept hoping someone else with a larger environment would get to the bottom of it, but they never did.
My tenacity finally kicked in with the final PMR opened in early Summer 2011. I worked it continuously with IBM for approximately a year. The end result was APAR OA40210, opened Aug 2012. IIRC, it was marked HIPER and DATALOSS, but didn't make it to Red Alert status.
I never asked for (and IBM never offered me) a copy of the ADRDSSU source code and, though I believe myself to be an excellent diagnostician, in all honesty it's unrealistic to believe I could have solved this any faster by myself, even if IBM had given me full access. The learning curve and time commitment required for someone not intimately familiar with the code to solve an elusive problem are immense.
-- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
