Edward Jaffe wrote: > But, even some support technicians at IBM are afraid of > reading dumps. I've experienced numerous situations in which it > was obvious that Level 2 was doing everything possible to > avoid that "chore" -- sending me off to gather input > parameters, logs, attempt additional recreates, etc. when all > anyone had to do was crack open the dump for a few minutes > (with the program listing handy) to understand what went wrong!
Heh heh... A couple of years ago a customer of ours had a loop when calling one of our Java programs. From the dump (including eventually a branch trace), I determined that the loop was entirely in the IBM JVM, and told them so. They insisted that we were repeatedly calling a Java function. > It's amazing how quickly things progress when people start actually > focusing on the wealth of information provided by the dump! In this case (and sadly, in a number of cases I've encountered) they didn't want to listen. I eventually figured out the offset of the bad loop test in the (OCO of course) JVM, and told them to look at their PL/X generated listing at that offset in DLL so-and-so. Naturally I expected a medal from IBM... :-) Instead an APAR fix was issued without comment or acknowledgement. Such is life at the bits & bytes end of ISV land. Tony H. ---------------------------------------------------------------------- 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
