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
