Without procuring a software product not already in house, I suggest using native z/OS SLIP trace. You can follow the execution path, capture registers and data, and even--though risky--alter exit logic to test fixes/improvements, all without paper work rigamarole. No intention to demean any of the fine products mentioned, but this is a way to do it all without management intervention.
. . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Chuck Arney <[email protected]> To: [email protected], Date: 10/10/2013 09:37 AM Subject: Re: Debugging IEAVMXIT Sent by: IBM Mainframe Discussion List <[email protected]> You could use our Trap Diagnostic Facility product for this. The Break Hook facility can be used to dynamically hook the exit and you can specify the job/task name of a single task that you want to trap and use to debug. All other callers of the exit continue to execute as normal. Chuck Arney Arney Computer Systems -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Norgauer Sent: Thursday, October 10, 2013 10:34 AM To: [email protected] Subject: Debugging IEAVMXIT Having a problem with IEAVMXIT(exit routine) I need to get diagnostic info when this exit executes. It is in a test LPAR so not that much going on there. What's the best way to debug this exit? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
