Thanks for the mention Martin. We are the new kids on the block so we don't have shops that have been using TDF for 20 years. Trap Diagnostic Facility (TDF) uses a very different internal design than other debuggers. Being that we are the "new kid" our architecture uses the latest z Systems facilities supported by the hardware. We run over a meg of code RMODE 64 and already support, or would exploit, some z Systems architecture features that are not even supported by z/OS yet. We are a full featured z/OS debugger specifically designed to make debugging multi-tasking applications easier. We have full support for Assembler application debugging, and perhaps some HLL debugging sometime pretty soon. And, we also have a non-interactive trace facility that lets you debug your code while it runs at full speed. And, yes you can even dynamically hook running jobs if you wish, at either a specific task level or at a code point executed by a specific job/task. No code changes at all needed to your code. No SVCs added to your system either. We are available when you are ready for the latest technology in debugging systems.
Chuck Arney Arney Computer Systems Web: http://zosdebug.com Facebook: http://www.facebook.com/arneycomputer -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, May 22, 2015 9:43 AM To: [email protected] Subject: Re: Debuggers Where is TDF? I do consider it pretty complete and very current using (where ever possible) TRAP facility- Which is IMHO superior to any other technique to intercept flow of a bare iron (HLASM) program. Since it is a pretty new development, supporting z architecture was an initial requirement. I am not associated in any kind with TDF. Well- one tiny little exception: my debugger (TRAPPER) does use TRAP (and all the associated stuff) in z/VSE.
