Should you encounter an error in the execution of your program, you can use the debugging facilities in AcuBench or ACUCOBOL-GT to investigate the problem. See Section 1.7.2 and Chapter 3 of the ACUCOBOL-GT User's Guide for a detailed description of debugger options and use. Once the debugger is running, it may be helpful to use the "tf" option to turn on file tracing. Included in the file trace are all calls to esqllib.dll. To generate the most detailed level of file tracing, follow "tf" with the number "9".
If you used the "-Po" switch when invoking the pre-compiler, you can look at the intermediate file created between pre-compilation and compilation for further debugging insight. These intermediate files can be opened into the Code Editor; however, you should not modify the intermediate files in any way.
When looking at an intermediate file, you may notice a unique directive called ">>IMP". This directive is automatically generated by the pre-compiler to reconcile file differences when:
1. The file has embedded SQL or an include file with copy books that use begin and end terminology. ">>IMP" will be used to specify where the embedded SQL, copybook, or file starts or ends in the original source file.
2. Files that contain both ANSI and terminal format types set begin and end points on data columns. ">>IMP" will be used to specify where the data columns start or end in the original data file.