Getting Startedwith pureQuery
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
358<br />
<strong>Getting</strong> Started with <strong>pureQuery</strong><br />
Through menu options and content assist, IBM Optim Development Studio can help you to<br />
create options files. It can help you to add interfaces and <strong>pureQuery</strong>Xml files to your<br />
options files, and it can help you add options. IBM recommends that you use Development<br />
Studio assistance to add <strong>pureQuery</strong>Xml files to your options files, rather than adding them<br />
manually. In order for the utilities to determine which options to use, the paths of<br />
<strong>pureQuery</strong>Xml files in the options files must exactly match the paths that IBM Optim<br />
Development Studio uses when it runs the utilities. Using assistance will ensure the paths<br />
match.<br />
E.4 Specifying option files on the command line<br />
E.4.1 Specifying an options file on the command line, without interfaces or<br />
<strong>pureQuery</strong>Xml files<br />
For the Generator, Configure, and StaticBinder utilities, you can use the option -<br />
optionsFile to specify an options file that contains the interfaces and <strong>pureQuery</strong>Xml<br />
files that you want the utility to process, along with the options that it should use for each of<br />
them. <strong>pureQuery</strong> processes each entry in the options file, in the order in which they are<br />
listed. Listing E.18.5 shows an example of specifying an options file.<br />
-optionsFile "C:\path\Default.bindProps"<br />
Listing E.18.5 - Example of specifying an options file that lists the interfaces and<br />
<strong>pureQuery</strong>Xml files to bind<br />
If you run a utility from the command line and specify an options file, you can specify some<br />
of the options on the command line as well. When you specify an option both on the<br />
command line and in the options file, <strong>pureQuery</strong> will use the value that is on the command<br />
line.<br />
E.4.2 Specifying an options file on the command line, in addition to<br />
interfaces or <strong>pureQuery</strong>Xml files<br />
For the StaticBinder utility, you can specify both an options file and interfaces or<br />
<strong>pureQuery</strong>Xml files on the command line. If you do this, <strong>pureQuery</strong> binds the interfaces<br />
and <strong>pureQuery</strong>Xml files that you specify on the command line, using the options that you<br />
specify on the command line, combined with the options in the bindProps file. For<br />
<strong>pureQuery</strong>Xml files, the path of the file that you specify on the command line must match<br />
exactly the path provided in the options file. Listing E.18.6 shows an example of specifying<br />
an options file and a <strong>pureQuery</strong>Xml file.<br />
-optionsFile "C:\path\Default.bindProps" -<strong>pureQuery</strong>Xml<br />
"C:\path\captureFile.pdqxml"<br />
Listing E.18.6 - Example of specifying an options file and a <strong>pureQuery</strong>Xml file on the<br />
command line
Change language