Recommendations for configuring and binding pureQueryXML files

Use the recommended options with the pureQuery Configure utility and StaticBinder utility when you prepare SQL statements to be run statically with pureQuery client optimization.

Options for the Configure utility

The following list describes recommendations for processing pureQueryXML files with the Configure utility:
  • Use the pureQuery Configure utility with the -cleanConfigure option when a complete capture is performed.
  • Use the -collection option to set the collection during a configure operation if you know the collection ID that will be used during the bind operation.
  • Use the -showDetails true option to include messages about the modification that are made by the application to the DB2® special registers.
    If you see the following message, the application might not run the same when executing SQL statements statically in the way it runs when executing SQL statements dynamically.
    The pureQueryXML file contains "n" Special Register SET statements or 
    methods that were recorded after other SQL statements were issued 
    using the associated Connection. 
    This might indicate that the file contains SQL statements that 
    were originally prepared using multiple, different special register settings.

    An example of an application that might run differently when executing SQL statements statically and dynamically is if statements are encountered first with a CURRENT SCHEMA of WEEK1_SALES, and later with a CURRENT SCHEMA of WEEK5_SALES. Such statements cannot be safely run statically if they contain unqualified names. It is possible, to use the Configure utility groupSQLBySpecialRegisters option as part of the process of configuring that application to run such statements dynamically.

Binding packages from pureQueryXML files

If the packages need to be bound only at specific isolation levels, use the StaticBinder -isolationLevel option to specify the isolation level.

Validating pureQueryXML files

If a problem occurs with the pureQueryXML file, you can validate pureQueryXml files by specifying the -validateXml TRUE option with the pureQuery utilities Merge, Configure, and StaticBinder. Any XML validation errors are displayed when the utility is run. The utility validates the input XML documents with the pureQueryXML schema.

Recommendation: IBM® strongly recommends that you edit pureQueryXML files by using the workbench only. If you edit a pureQueryXML file outside of the workbench, you risk making the file unusable.

If you manually edit a pureQueryXML file, be sure that you create a backup copy of the file first. Use the -validateXml option with the pureQuery Merge, Configure, and StaticBinder utilities to perform XML schema validation on input pureQueryXML files.


Feedback