Fault Analyser

[Margaret Hammond]

We have been asked to review whether Endevor can output a side file, IDILANGX for use with Fault Analyser at compile time.  The ideal situation is that when the .LISTING is output as part of CONLIST use that there is also an additional member written the the IDILANGX PDS for use when Fault Analyser comes into use for CICS or Batch abends.   At present we are manually generating the member in IDILANGX while in Fault Analyser pointing it to the relevant .LISTING already output by Endevor.   If this is not possible does anyone have any suggestions / guidance on what they do?  Many Thanks

[Dave Harding]

Hi Margaret,

Yes, the in-scope Generate processor(s) can be updated to include a step to
create the Fault Analyzer output. All you need is the JCL that's being
manually submitted- get that into the processor, right before the CONLIST
step, and update to use Endevor's &C1 symbols.

*Dave Harding *
Client Services Consultant • Mainframe Software Division
Broadcom Software
Mobile [phone] | [e-mail]
Upcoming vacation: June 13 - 15, August 10 - 23

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.

[Margaret Hammond]

Many thanks, will take a look at that.

[Margaret Hammond]

Originally I was getting RC0310.  

0310

Compiler listing file is not in the expected format. A possible reason is that the required compiler options have not been used.

I then used the LISTING PDS that was FBA (uncompressed) and it has now worked.   I  presume that is because the LISTING we produce is usually compressed?

[Dave Harding]

Yes, CONLIST writes the listing data in compressed format

[Joseph Stein]

Hi,

Endevor indeed has no problem creating the IDILANGX file.

This , however , is not the most efficient way to create DEBUG info for Fault Analyzer.

It is best to let the COMPILER generate the debug info with the  TEST parm into a //SYSDEBUG file which obviates the IDILANGX step completely.

If you use the NOSEPARATE sub-parameter with the TEST option , you don't even need a SYSDEBUG file as the DEBUG info is incorporated into the LOAD module.

The above assumes you are using a supported version of the Enterprise Cobol compiler. (V6 and above).