Hi Ed,
WRT "ColeSoft acquired zDebug many years ago" I
don't recall that we ever did that.
WRT "and incorporated much of that technology
into z/XDC." I'm sure we never did that.
z/XDC does have TRAP2 support, but we didn't
implemented it until sometime in 2018. (Peter Morrison did the work.)
Our TRAP2 support integrates pretty well into our
existing X'00'-opcode support. Users can use a
simple command (SET TRACE TRAP2|ZERO) TO switch
back and forth at will between the two forms of breakpoints.
The problem, of course, with TRAP2 support is
that the scope of TRAP2 activation is limited to
only those tasks (or SRBs) for which a Trap
Handler Exit has been linked into the DUCT. But
there is no z/OS supported mechanism for
automatically installing Trap Handler Exits into a task when one is needed.
There are two ways that I can think of to deal
with this. One is to place intercepts in z/OS's
ATTACH service that adds Trap Handler Exits (when
appropriate) at task creation time. (This is NOT what z/XDC does.)
The other is to monitor for PIC 0013 (which
becomes abend 0D3-13 an ESTAE time) and install
the missing Trap Handler Exit at TRAP2 instruction failure time.
I don't know what Chuck Arney does, but
monitoring for the 0D3-13 is what z/XDC does.
The problem here, of course, is that you'd think
you could dispense altogether with z/XDC running
as an ESTAEX if you use TRAP2 instructions, but
you can't. (At least not yet you can't.) You
still need z/XDC to exist as an ESTAEX in order
to catch the 0D3-13 abends so that it can know
when Trap Handler Exit setup is needed. [sigh]
However, the good news is that I'm currently
working on easier ways to cause Trap Handler
Exits to be installed. I expect to have that
published in a month or few. Then it will become
much more feasible to let z/XDC use TRAP2-type
breakpoints without z/XDC also having to be present as an ESTAEX.
This will make debugging much easier for programs
having numerous, ephemeral ESTAEs popping up
everywhere. (LE code is an example of such.) This
will definitely help our c/XDC users a lot! (Our
assembler customers should like it too.)
Dave Cole, Developer
dbc...@gmail.com (personal)
dbc...@colesoft.com (business)
540-456-6518 (cell)
At 3/1/2023 11:34 PM, Ed Jaffe wrote:
On 3/1/2023 4:01 PM, Bernd Oppolzer wrote:
Am 01.03.2023 um 19:51 schrieb Martin Trübner:
I know of one big z/OS installation that has a
debugger in use that uses TRAP (and the author is on IBM-main as well)
That's me ... but as I said in the other mail,
I am not the author of the debugger;
I am only the maintainer today, and I changed
the breakpoint mechanism (was: S0C1) by TRAP in the 2010 time frame.
He might have been referring to z/XDC. ColeSoft
acquired zDebug many years ago, which used TRAP
exclusively, and incorporated much of that technology into z/XDC.
IIRC, you must use the 0C1/ESTAEX method only
once at initial entry. After that, you can
switch over to TRAP (which is advantageous)...
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
