Enterprise Developer offers some powerful tools to help you debug local and remote projects. It also supports debugging of standalone files which are not part of a project. This is a brief overview of how to prepare and debug an application.
If Project > Build Automatically is turned off, to compile click Project > Build Project.
Eclipse opens the Debug perspective that provides views that facilitate debugging.
See Debugging features and techniques in Eclipse for tips on the commands and features that are available during debugging.
You can use the IDE to debug a standalone native COBOL program/application that is not a part of a project. The file(s) must be compiled for debugging first to produce the .idy file containing the information that the debugger requires.
The debug engine, by default, takes the location of the source files from the .idy file, which is usually the location from which they were originally built; however, if you move your source files, you can override this from the Source tab in the debug configuration (for the source files) and from the preferences dialog box for the copybook files. This allows the files to maintain their context when being debugged.
To debug a standalone file:
Eclipse either used the Compiler directives provided by the associated program symbols file (.idy) or, if no .idy file is present, uses the directives specified in Window > Preferences > Micro Focus > COBOL > Standalone Files > Compile.
This starts debugging and the IDE switches to the Debug perspective.