I have seen a number of support cases recently where the correct tool to use in identifying the cause of an issue was to use the FGLSQLDEBUG environment variable.
I find using the FGLSQLDEBUG valuable in telling me what the SQL statement sent to the database is, what the parameters sent were, and what the results sent back were. Too often I see developers focusing on the 4gl code in thinking what the SQL statement executed is, when particularly with databases other than Informix, the ODI layer is going to transform the SQL syntax from the Informix syntax to the appropriate syntax for that database. The important thing is what was actually executed on the database.
In this article I introduce FGLSQLDEBUG, look at some FGLSQLDEBUG output and show you what to look for in the output.
Read the article at
https://4js.com/ask-reuben/ig-83/
Sign in for full access
Help
