Craddock, Chris wrote:
[snip]
If you DO that, then your debugging environment is completely baked into
your code, but there is no physical dependence on XDC and no way for fat
fingered programmers to blunder into it. A certain family of products
that I've had a passing association with :-) are -ALL- like that.
Recovery and diagnostic support is always there no matter what. And if
XDC is present and you're properly authorized, you can just use it. If
it's not present, or it is, but you're not authorized for it, you don't
even know its there.
No muss, no fuss. No worries.
Yup! I deliberately didn't go there because the typical non-ISV user
probably won't feel the need to integrate with z/XDC to that extent.
However, this level of integration, exactly what Steve Thompson was
alluding to in his post, is a *must* if you're going to debug exotic
code (e.g., SRB mode -- which can't be HOOKed in the traditional way)
and/or you want to be able to use and/or debug your recovery routines
during a z/XDC session. I'll bet most savvy ISVs are doing it just like
you described!
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
