Rick said > I've looked at XDC, but it doesn't seem to lend itself easily > to imbedding in an application that might very well be a "OEM Software > Product". It appears to be a great debugging tool, but I question the > advisability of imbedding it in a fee-based product.
You don't need to embed it to integrate it, even in shipping ISV code. Dave and others have mentioned the HOOK command - which works exactly as advertised. But there is another way to integrate XDC with your code. The only "trick" you need is to call XDC from your own recovery code, passing the SDWA in the same manner that your own code got it from RTM. When XDC returns control you do whatever the RC indicates. If you got a 4, then Dave has already done everything for you and you just return to RTM. If you get anything else you go on about your business and handle recovery. There are a few minutiae about handling "END COMPLETELY" and conditionally establishing addressability to XDC - left as an exercise to the reader. 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. CC ---------------------------------------------------------------------- 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
