Thanks for the update John. Good to know.
Peter
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of John Ehrman
Sent: Friday, May 22, 2015 2:32 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Debuggers
Peter Farley noted
I've had the opportunity to work with Xpeditor, IBM Debug Tool, and XDC.
They all do a good job. I use XDC now, almost daily, and it's what I'd
recommend to assembler developers.
I really liked Debug Tool a lot, but it's complicated to set up and
difficult to learn (at least in my experience a
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.
At 5/22/2015 02:32 PM, John Ehrman wrote:
More recent versions of ASMIDF do support debugging of batch jobs.
yeah, and they (John, or someone who worked for John) came up with
The really cool name for it: Batch Connect, and I am totally
jealous of that name.
Our z/XDC has had, of course,
Peter Farley noted about ASMIDF (in part):
(Start)
The last time I used it, there was also no capability to directly debug an
executing batch job like z/XDC and other HLL language debuggers provide.
(End)
More recent versions of ASMIDF do support debugging of batch jobs.
Regards... John
I did use that one John, before I had access to z/XDC. It was possible to
debug using it, but the line-mode orientation of the interactive interface was
painful to use. Also very painful to use was the ASMADATA conversion part of
the tool, because the local compile toolset does not permit
Have any of the responders to the original query used ASMIDF, the debugger
in the High Level Assembler Toolkit Feature? It's tailored specifically
for assembler applications.
John Ehrman
