The Eclipse IDE provides the following mechanisms for linking compilation errors to the offending lines of code and also reports ADMLP, MAP or LINK errors that might have occurred during the build in the Problems view:
You can click a compilation error message, and the Eclipse IDE automatically opens the editor to the line of code that contains the error.
When the editor is open, offending lines of code are flagged with the appropriate compilation diagnostic, such as error, warning, and so forth.
If the compilation occurs without the "S" option, the ACOB listing parser assumes that the last six characters of the error line are the line number and uses that as the location in the source for attaching the error tag.
If build runstream problems prevent Eclipse from learning the source file name, or the source file does not seem to be a valid member of the project, errors that are detected in the console or breakpoint output files are attached to the project.
The build of an OS 2200 project produces an output console view for each project built and each registered bkrpt file produced by that build.
The build of an OS 2200 project produces an entry in the End Line Summary view for each line of build starting with “END”. Click on the first column of an entry to view a dialog with the output lines from the most recent ECL statement to its corresponding "END" line.