>Go through a SYSTRACE and parse out the trace entries of interest, >then do IP WHERES on the PSW addresses to get the displacements in the >modules. Generate side by side listing of trace entry, psw address, r15, >r0, r1 and the module name and displacement.
That is one thing I had written a verbx for when I was IBM. It helped to analyze loops and performance problems. It would have been nice to have an IPCS command that does the IPCS WHEREs automatically, taking into account if the psw is in private of an address space that is not dumped or for sadumps use the correct settings for the xmem environment (for addresses in private). That still leaves the task of manually doing the offset findings in the huge lmods like iefw21sd or igdzilla or (heaven help) libnotes or dsmc... >Some have suggested that we add an option to WHERE, >filtering based on data type. The most common filter that has been >proposed is a MODULE data type filter. It would be interesting to hear >opinions on this suggestion from regular IBM-MAIN contributers I am not sure I understand what is proposed here. What would a module data type filter do to WHERE (or systrace)? As for GFS traces - in IBM Germany we had someone writing a COBOL program to do that analysis for us (I had the dubious honour of fixing a bug in it - my one and only forray into Cobol). I know that IBM P'keepsie has a similar tool to do the analysis. It would be nice to get that (or something similar) incorporated into IPCS - saves the ingenious editing via IPCS print file that I usually do.) Regards, Barbara Nitz -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse für Mail, Message, More +++ ---------------------------------------------------------------------- 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
