Example 11 “example of errors and warnings, Shown for sql statements – HP Integrity NonStop H-Series User Manual
Page 93

Example 11 Example of errors and warnings shown for SQL statements
Unfortunately, the .sqlmxStatements.txt and .sqlmpStatements.txt are read only when
Eclipse is started. So you must restart Eclipse after creating a project before erroneous errors will
be removed from editors.
Example 12 “Errors for get_dept_rec”
shows the same editor and file as
of errors and warnings shown for SQL statements”
does, but after restarting Eclipse. Though many
erroneous errors have been removed, some still remain. Most of the erroneous errors are caused
by the SQL record get_dept_rec because it is not defined for C. To workaround this sort of
error, you can add get_dept_rec to the .sqlmxStatements.txt file, but you must restart
Eclipse before CDT will read the .sqlmxStatements.txt file again.
NOTE:
Because C macros are case sensitive, the .sqlmxStatements.txt and
.sqlmpStatements.txt
files contain three versions of each SQL statement—one in uppercase,
one in lowercase, and one in lowercase except for the first letter. If you use other variations of
case in your code, you will need to add those variations to the appropriate SQL statements file.
Removing erroneous errors and warnings in C/C++ editors
93