Getting Startedwith pureQuery

7.2.2.3 Changes to pureQueryXml files
Chapter 8 – Extended Insight 141
If you are using the StaticBinder to bind the statements in a pureQueryXml file that you
created by using the capture functionality of the Client Optimizer, you must use the
Configure utility to process the file before you use the file with the StaticBinder utility. You
must do so anytime you alter the file, either by performing an incremental capture or by
editing it manually. If you do not process the file with the Configure utility, your application
could have unexpected results during static execution. If you are using a pureQueryenabled
file in IBM Optim Development Studio, the tool runs the Configure utility for the
pureQueryXml files in the pureQueryFolder directory automatically.
Tools that integrate with pureQuery have pureQueryXml files that are created without using
the pureQuery capture capability. These tools are .NET, CLI, JPA, and Hibernate. Chapter
17 discusses the integration with JPA. The integration with .NET and CLI is beyond the
scope of this book. As with files created using pureQuery capture, you must use the
Configure utility to process pureQueryXml files for .NET and CLI after the files are created
or altered. The files that are created for integration with JPA and Hibernate do not need to
be configured, and the Configure utility cannot process them.
IBM recommends that you only modify pureQueryXml files by using tools provided by IBM.
These include capturing, configuring, and using the IBM Optim Development Studio
pureQueryXML editor. If you modify pureQueryXml files manually, they could contain an
unexpected or invalid combination of values. The Configure utility can correct or identify
some of the problems that manual editing can cause. Therefore, IBM particularly
recommends that you do not manually edit the pureQueryXml files that are created for JPA
and Hibernate.
7.3 Specifying options for the StaticBinder utility
pureQuery provides multiple utilities. All of these utilities allow you to specify options on
the command line. For the StaticBinder utility and some of the other utilities, you can
specify the interfaces and pureQueryXml files that you want the utility to use, along with the
options it should use for each interface or file, in a type of file that is known as an options
file. Refer to Appendix D for a description of options files. pureQuery allows two types of
options files: genProps and bindProps. The StaticBinder utility uses bindProps files.
An options file is a text file that lists interfaces and pureQueryXml files to be processed,
and the options to apply to each interface or file. For pureQueryXml files, you can use a
colon and the name (:MYPKGA, for example) of a statement set to indicate that the options
on the line apply to only the specified statement set. Each interface and pureQueryXml file
must be listed on a separate line in the options file, followed by an equal sign (=), and then
any options that pureQuery should use when it processes that item. Additionally, in each
options file, you can provide default options on a line that starts with defaultOptions.
pureQuery uses each option that you specify on the defaultOptions line for all the
items, except for those items for which the option is specified with a different value. Listing