For Cobol programs, FA requires the use of the XREF option. This created a problem for us when we migrated because most of our programs were compiled without XREF (to save space). We ended up writing a special utility program to extract the Cobol source from the listing and then recompile it with XREF turned on. The new compile listing (which was discarded after the process) was then used to generate a side file using a FA utility program. The side file was stored in a PDS that we maintain in parallel with the compile listings.
We knew that this process would not be 100% reliable (because of compiler versions and PTFs, as you pointed out), but it has proved to be "good enough" for our purposes. "Good enough" meaning that FA was able to interpret Working Storage correctly, which is really all you need to solve run-of-the-mill application abends. On Wed, Feb 10, 2010 at 10:18, Farley, Peter x23353 < [email protected]> wrote: > I stand corrected. Thanks for the info. > > Does FA require the ADATA info as I was told, or can it operate only off > the compiler listing without ADATA? Needing to produce and archive > ADATA going forward with FA would be a problem because pre-existing > compiles would not have that data captured. Recompiling to produce > ADATA would not always work either, because compiler versions and/or > PTF's may have been updated between the original production compile date > and the date of the abend. That could (but might not) invalidate the > analysis or point to the wrong place in the source. > > Peter > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > > Behalf Of John P Kalinich > > Sent: Wednesday, February 10, 2010 10:06 AM > > To: [email protected] > > Subject: Re: Compuware FileAid to IBM FileManager Conversion > > > > Peter Farley of the IBM Mainframe Discussion List > <[email protected]> > > wrote on 02/10/2010 08:26:27 AM: > > > > > I am told by my sysprogs that Fault Analyzer requires the ADATA > output > > > file of the compiler to be allocated in the production JCL in order > to > > > analyze production abends the first time they occur. This is a > > > non-starter for us, thousands of JCL's would have to change. YMMV. > > > > You can specify the compiler listing PDS names in the Fault Analyzer > > PARMLIB member IDICNFxx, so you do not have to change any JCL. If the > > compiler listing is not available, FA will perform a real-time > analysis of > > the abend, but it will not use any source code information. > > > > After the fact, FA can perform an interactive re-analysis of the abend > > using the information written to the FA History file. Before > re-analysis, > > FA will prompt you for a compiler listing file. This gives you the > option > > to compile after abend and let FA use that source code information. > > > This message and any attachments are intended only for the use of the > addressee and > may contain information that is privileged and confidential. If the reader > of the > message is not the intended recipient or an authorized representative of > the > intended recipient, you are hereby notified that any dissemination of this > communication is strictly prohibited. If you have received this > communication in > error, please notify us immediately by e-mail and delete the message and > any > attachments from your system. > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
