The pureQuery Configure and StaticBinder utilities use pureQueryXML files as input. When you run your non-pureQuery API application so that captured statements run statically, pureQuery uses pureQueryXML files, too.
For the most part, pureQueryXML files contain information about only those SQL statements that ran successfully. However, batched statements are captured even if all statements in a batch fail to run successfully.
Recommendations: Because pureQueryXML files are central to the entire process of running SQL statements statically, do not edit pureQueryXML files manually. Attempts to modify a pureQueryXML file risk causing subsequent capture, configure, merge, or bind operations to fail. Moreover, a damaged pureQueryXML file can cause errors when you run your non-pureQuery API application with executionMode set to STATIC. Also, do not develop applications that process pureQueryXML files. The structure of pureQueryXML files might change.