Ensure that your system meets the hardware and software requirements. See System requirements for InfoSphere® Optim™ pureQuery Runtime.
The pureQuery Runtime utilities can be run from the command line with a command that invokes Java. To run the utilities, the JAR files pdq.jar, and pdqmgmt.jar must be on your classpath.
If you are running the Configure utility and specify either the -replaceLocations or the -replaceSchemas option, the JAR file pdqsqlparser.jar must also be on your classpath.
If you are running the StaticBinder utility and specify the -singletonSelect option, the JAR file pdqsqlparser.jar must also be on your classpath and you must use Java runtime environment version 6 or later.
For utilities that connect to a database, you must also have the database driver JAR files on your classpath. For example, the files for IBM® Data Server Driver for JDBC and SQLJ are db2jcc_license_cu.jar and db2jcc.jar. You use these driver files to connect to DB2® for Linux, UNIX, and Windows database. For example the GeneratePureQueryXml, ManageRepository and StaticBinder utilities require a connection to a database.
To add the JAR files to your classpath, you can modify the CLASSPATH environment variable or use the Java -cp option. For information about the CLASSPATH environment variable and the -cp option, see your Java documentation.
set CLASSPATH=C:\pureQuery\pdq.jar;C:\pureQuery\pdqmgmt.jar;.;%CLASSPATH%;
java com.ibm.pdq.tools.Configure -pureQueryXml mytestsql.pdqxml -rootPkgName MYTEST -validateXml TRUE
set CLASSPATH=C:\pureQuery\pdq.jar;C:\pureQuery\pdqmgmt.jar;db2jcc_license_cu.jar;db2jcc.jar;.;%CLASSPATH%;
set pqconnect= -repositoryURL jdbc:db2://localhost:50000/SAMPLE -repositoryDriverClass com.ibm.db2.jcc.DB2Driver
java com.ibm.pdq.tools.ManageRepository %pqconnect%
-repositoryUsername "test" -repositoryPassword "testpwd"
-create repository -repositoryType pureQueryOnly
The ManageRepository command is on multiple lines for readability. In the batch file, the command on a single line.