IBM Mainframe Discussion List <[email protected]> wrote on 01/04/2007 04:27:45 PM:
> On Thu, 4 Jan 2007 14:52:02 -0500, Jim Mulder <[EMAIL PROTECTED]> wrote: > > >... > > The routing to WTO SSI function routines is done by SSI, not > >Console, so the SYSOPS CTRACE will not help you a snapshot > >after each function routine. Your choices would be: > > > >1. SLIP IF,A=TRACE in IEFJRASP with a DATA filter on the SSI > > function code. IEFJRASP is OCO, so you would need assistance from > > MVS SSI Level 2 to construct the SLIP. > > > >2. Write an IEFJFRQ exit. This is documented in the > > "MVS Istallation Exits" manual. > >... > > I suspect there is a 1.5 option also. Set a SLIP trace on a dummy > IEFJRASP since the exit is documented. It's been a long time since I've > set up a SLIP trace. (Last time was looking for the Unix dirty bits in > TCBs. Honestly! It was.) > > I was going to say, given your response, that maybe I'd just wait until > NetView lvl 2 suggested what I do to debug this. But they just did. They > just suggested a COMP=SYSOPS CTRACE. <sigh> > > That would give me the WQE after the SSIs are done with it? Not exactly > what I was hoping for. There is a SYSOPS CTRACE record created at the completion of SSI processing, so that should allow you to answer the question "did some subsystem modify the WQE?". If that answer is Yes, then the SLIP trace (option 1 or 1.5) would be the next step in figuring out which subsystem modified the WQE. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
