To open this file in an editor in the workbench, double-click it. The file is located in the folder dataAccessFolder in your Java™ project.
In this file, you can specify options that apply to all of the pureQueryXML files that are in your project. You can also specify options specific to individual pureQueryXML files.
You can add comments to this file. Begin each comment with a # symbol.
As you create or edit entries, you can type CTRL+SPACE (or your own keystroke, if you changed this default one) for assistance.
For help understanding syntax diagrams, see How to read syntax diagrams.
The following diagram shows the syntax that is allowed for setting default options in this file.
>>-defaultOptions--=--+- -bindOptions-- -"--bind-options--"-+---> | (1) | '-| DBRM options |--------------------' >--+-----------------------------+--+----------------+----------> | .-FALSE-. | | (2) | '- -differenceOnly--+-TRUE--+-' '-| -grant |-----' >--+-----------------------+----------------------------------->< | (3) | '-| Trace options |-----'
The next syntax diagram shows the syntax that is allowed for setting options for individual pureQueryXML files that the file lists.
>>-+-pureQueryXML-file-----------------------+--=---------------> '-pureQueryXML-file--:--base-package-name-' >--+- -bindOptions-- -"--bind-options--"-+----------------------> | (1) | '-| DBRM options |--------------------' >--+-----------------------------+--+----------------+--------->< | .-FALSE-. | | (2) | '- -differenceOnly--+-TRUE--+-' '-| -grant |-----'
The value for each option cannot contain spaces.
For a list and descriptions of these options, see BIND command.
If you use the CONCURRENTACCESSRESOLUTION bind option in DB2 Version 9.7 for Linux, UNIX, and Windows, the option applies to all of the statements that are in packages that are bound at the CS and RR isolation levels. This option, which applies only to these two isolation levels, lets applications find the last committed value in rows that are locked by other applications.
After the StaticBinder utility generates the DBRM files, you must copy the files to a data set. The default DBRM data set name is prefix.DBRMLIB.DATA, where prefix is the high-level qualifier that is specified in the TSO profile for the user. prefix is usually your user ID in TSO.
If the DBRM data set does not already exist, you must create it. The DBRM data set requires space to hold all the SQL statements, with additional space for each host variable name and some header information. The header information requires approximately two records for each DBRM, 20 bytes for each SQL record, and 6 bytes for each host variable. For an exact format of the DBRM, see the DBRM mapping macro, DSNXDBRM in library prefix.SDSNMACS.
The following syntax diagram describes the options for generating DBRM files.
.-FALSE-. >>- -generateDBRM--+-TRUE--+-- -outputDBRMPath--path-----------><
The root name of the generated DBRM files is the root package name that you specify when you run the Configure utility.
The default is FALSE.
For example, suppose that you run the StaticBinder utility on a pureQueryXML file named capture.pdqxml. The utility creates the packages MYPKGA, MYPKGB, and MYPKGC. Then you edit the statement set MYPKGA in capture.pdqxml with the workbench and run the Configure utility on the file with the -cleanConfigure option at its default value of FALSE. The Configure utility assigns a new consistency token to the statement set because the set has changed. When you run the StaticBinder utility on capture.pdqxml again to bind the new version of MYPKGA, you specify -differenceOnly TRUE. The utility rebinds only MYPKGA and does not rebind the other two packages.
The default value is FALSE.
.-,--------------------. V | >>- -grant-- "--grantees--(----+-authorization-ID-+-+--) - "--->< '-PUBLIC-----------'
For DB2 Database for Linux, UNIX, and Windows: You can use the USER, GROUP, and ROLE keywords. For information about these keywords, see GRANT (Package Privileges) statement.
For DB2 for z/OS: You can use the ROLE keyword. For information about this keyword, see GRANT (package privileges).
Restriction: You cannot use the -grant option when the value of the -generateDBRM option is TRUE.
The isolation level applies to all of the SQL statements that are in the package. If you set an isolation level through the Connection.setTransactionIsolation() method of the IBM® Data Server Driver for JDBC and SQLJ, pureQuery™ ignores that isolation level for statements executed statically.
The name of this file must end with the extension .pdqxml or .xml.
The file must be a resource in the classpath for your application.
>>-+------------------------+--+---------------------------+--->< '- -traceFile--file-name-' | .-OFF-----. | '- -traceLevel--+-ALL-----+-' +-SEVERE--+ +-WARNING-+ +-INFO----+ +-CONFIG--+ +-FINE----+ +-FINER---+ '-FINEST--'
If the file already exists, pureQuery appends new messages to the existing content of the file. As the default, the entries are written to System.err.