pureQuery keywords supported by CLI and .NET applications

When you enable a CLI or .NET application with pureQuery client optimization, you configure the pureQuery client optimization by specifying keywords and values in the application configuration file.
The following table lists the pureQuery Runtime properties that can be used with CLI or .NET applications as pureQuery keywords. Not all pureQuery runtime properties are supported by CLI and .NET application that are enabled with pureQuery client optimization.
Table 1. pureQuery properties supported by CLI and .NET applications enabled with pureQuery client optimization
Property Description
allowDynamicSQL1 Specifies whether to allow an application to run the following types of SQL statements dynamically: SQL statements that are not captured in a pureQueryXML file, and SQL statements that are captured in a pureQueryXML file but which have not been bound by the StaticBinder utility.
capturedOnly1 Specifies whether to run only the SQL statements that are in the pureQueryXML file.
captureMode Specifies whether to capture information about SQL statements.
enableDynamicSQLReplacement1 Specifies whether to run alternative SQL statements in a pureQueryXML file, where neither those alternative statements nor the corresponding original statements were bound by the StaticBinder utility.
executionMode Specifies whether to run statically the SQL statements that have been previously captured and stored by pureQuery Runtime.
maxNonParmSQL1 Specifies the maximum number of non-parameterized SQL statements to capture. This option applies only when the value of captureMode is ON. When captureMode is OFF, pureQuery ignores this parameter.
propertiesGroupId1 Specifies a runtime group ID in a repository that is created in a database. pureQuery Runtime uses the runtime group ID and the connection information that specifies the repository to retrieve pureQuery runtime configuration and pureQueryXML file information.
pureQueryXml Specifies the fully-qualified or relative path to and name of a file that is to be created by the process of capturing SQL statements or that already exists as a result of that process.
pureQueryXmlRepository1 Specifies the repository that contains the pureQueryXML file data that is used with a CLI or .NET application enabled with pureQuery client optimization.
repositoryRequired1 Specifies the pureQuery client optimization behavior if errors occur during retrieving pureQuery data. If the pureQuery runtime properties and pureQueryXML data cannot be retrieved from the location specified by the pureQueryXmlRepository property.
sqlLiteralSubstitution1 Specifies whether to perform literal substitution. pureQuery Runtime attempts to replace literal values in SQL statements with parameter markers and run the parameterized versions of the statements.
traceFile Specifies the file to write the log into. You can use an absolute path or a path that is relative to the directory in which the pureQuery Log utility runs.
traceLevel1 Specifies the level of detail to write to the log file.
1 Supported by pureQuery for .NET applications with IBM Data Server Driver Package V9.7 Fix Pack 6 or later.

Usage notes

  • pureQuery Runtime keywords can be specified as an application connection property, in db2cli.ini file for both .NET and CLI applications, or in a db2dsdriver.cfg file for CLI applications. If a keyword is specified in multiple locations, the order of precedence from highest to lowest is as follows:
    • Application connection property
    • db2cli.ini file
    • db2dsdriver.cfg file
  • pureQuery Runtime checks for a valid pureQuery license if any of the pureQuery Runtime keywords are specified in a configuration file. If the valid pureQuery license is not found, pureQuery Runtime ends and returns the error code SQL8029N.
  • pureQuery Runtime checks the following keywords in a CLI or .NET application environment. If the keywords are not set to their default values and pureQuery Runtime determines that a pureQueryXML file is required:
    • capturedOnly
    • captureMode
    • enableDynamicSQLReplacement
    • executionMode
  • If a pureQueryXML file is required but not specified, pureQuery Runtime throws the error CLI0124E Invalid argument value. SQLSTATE=S1009

Feedback