Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

The FaultFinder tool appears to be missing from Visual COBOL

The FaultFinder tool appears to be missing from Visual COBOL

Problem:

Under Visual COBOL, the tool named FaultFinder appears to be absent.

Resolution:

The FaultFinder tool, which had been available in the Server Express and Net Express products, has been removed from the Visual COBOL and Server for COBOL products on both Windows and Linux/UNIX.  Here is a documentation link mentioning this:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.cobolruntime.win/GUID-B77D3A01-EB52-4775-99D8-0EFB9AAE8D37.html

The main alternative diagnostic tool in place of FaultFinder is the Consolidated Tracing Facility:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.cobolruntime.win/HRCTRHUCTF01.html

For Native COBOL applications, another alternative is Debugging Using a Core Dump. This is similar to FaultFinder, because it allows the state of an application to be saved to disk in a core dump file when the application crashes.  You can then use the dump file to help debug problems, as it indicates where in the source code the error occurred, along with the values of variables, expressions, and the contents of memory as they were at the moment the error occurred:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.visualcobol.vs2015/HHDGCHDEBG09.html

Another alternative for Native COBOL applications is Just-In-Time Debugging, which allows a debugger to be connected to a running application at the moment an error occurs:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.visualcobol.vs2015/GUID-1DAAD120-1845-47DC-93B6-61276C7E2CD9.html

If the application is running on a production machine separate from the workstation on which a developer is running the Visual Studio for Visual COBOL IDE, the application can be debugged using Remote Debugging, as described here:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.visualcobol.vs2015/GUID-797E8732-2483-494A-AA4E-B942A1F6A065.html

For applications and services running under Enterprise Server, a person can take these debugging approaches:

http://documentation.microfocus.com/help/topic/com.microfocus.eclipse.infocenter.visualcobol.vs2015/HHDGCHDEBGF1.html

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2016-11-01 14:19
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.