I don't recall using it for this particular exit, but I've used it for others. The doc on setting up a SLIP trace is pretty good. You run GTF trace with TRACE=SLIP. If you have trouble locating the module, try using SETPROG to load it in LPA:
setprog lpa,add,MODNAME=IEAVMXIT,dsname=sys1.linklib After you stop GTF, run IPCS against the trace data set:. IPCS NOPARM DROPD DDNAME(GTFTRACE) SETD NOCON NODSN LIST GTF DDNAME(GTFTRACE) END By default (IIRC) you get all regs. You can also request data by address (such as 1R??) for whatever length you specify. You can limit the SLIP trace to a single job to reduce the data you collect. . . 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: John Norgauer <[email protected]> To: [email protected], Date: 10/10/2013 02:44 PM Subject: Re: Debugging IEAVMXIT Sent by: IBM Mainframe Discussion List <[email protected]> I have used z/OS SLIP trace for batch assembler programs, but not an exit. Is there any issue with an exit and using SLIP? John Norgauer Senior Systems Programmer Mainframe Technical Support Services University of California Davis Medical Center 1651 Alhambra Blvd Suite 200 Sacramento, Ca 95816 916-734-0536 SYSTEMS PROGRAMMING...... Guilty, until proven innocent !! " JN 2004 ........ "Hardware eventually breaks - Software eventually works" anon ........ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
