Going through your build reports
After a build, open your ERROR_FILES folder.
For assistance understanding your build reports, please email the error.tgz file to GMCL for analysis.
To begin analysis of your build reports yourself, open your ERROR_FILES folder, then the MOST RECENT folder.
- Sort these files from largest to smallest by clicking on the Size column header.
- For now, ignore the DBDOC.ERR and DBDOC_SUMMARY.ERR files.
- Look at files larger than DBDOC_RESIDUAL.ERR. The first files to look at are DBDOC_*.ERR files (not DBDOC-CHECK_*.ERR or DBDOC-IGNORE_*.ERR). These should provide excellent clues to how successful your build was.
- Alternatively, you may sort the folder by filename. Take a look at all the errors named DBDOC*.ERR, but not DBDOC-CHECK*.ERR or DBDOC-IGNORE*.ERR. These should also provide some excellent clues. Each of these files is documented in Build reports.
- It may be helpful to choose to build the build report files into your M14 as a BuildPlus option.
- Build reports can be compared between builds using WinMerge (explained in Other error checking techniques)
Note: Remember that when analyzing these files there is more information available for cross-analysis in the build folder, such as Unused_Tags.txt and Unused-alarm_tags.txt. For more details, see General build reports. If you have any questions, please don't hesitate to call us!
Email: geoff@gmcl.com
Toll Free: 1-866-438-2101 in U.S. and Canada
Phone: +1 780 438-2101 outside U.S. and Canada