Example of listing pureQueryXML files and statement sets in options files

The StaticBinder utility always processes the entries in options files in the order in which they are listed. If an options file contains both an entry for a statement set in a pureQueryXML file and an entry for that entire pureQueryXML file, the order in which the entries appear determines the output for those entries.

An entry for a statement set looks like this:

file.pdqxml:base-package-name
The base name of the package is the value of the name attribute of the package element that describes the package in the pureQueryXML file. The base name consists of two parts:
  • The root package name
  • Any characters that the Configure utility appends to the root package name when more than one package name is needed. For example, the utility creates more than one package name when the number of SQL statements in a statement set exceeds value of the Configure utility -sqlLimit option.

The examples in the next two sections use the following objects:

captureFile.pdqxml
This pureQueryXML file contains four statement sets with the following base package names: PKGA, PKGB, PKGC, and PKGD. Each of the statement sets contains SQL statements that use the table TABLE1. In all of these SQL statements, TABLE1 is referenced as TABLE1, not as schema-name.TABLE1. Each entry in the options file uses the -bindOptions option to specify the QUALIFIER option, which determines the schema name for tables that are referenced without schema names.
captureFile.pdqxml:PKGA
This statement set requires particular options, and so it has a separate entry in the options file.

For these examples, recall that when you bind a statement set without specifying an isolation level, the StaticBinder utility creates four packages, one package for each isolation level. Suppose that you ran the StaticBinder on PKGF, but you did not specify an isolation level. The StaticBinder utility would create the packages PKGF1, PKGF2, PKGF3, and PKGF4, each appended number indicating the isolation level for the package.

Examples that result in one version of PKGD

Examples that result in two versions of PKGD


Feedback