What's new in InfoSphere Optim pureQuery Runtime Version 3.2 releases

Product documentation


Abstract

This document describes the new features and enhancements in InfoSphere Optim pureQuery Runtime for Linux, UNIX, and Windows and in InfoSphere Optim pureQuery Runtime for z/OS.

Content

pureQuery Runtime version:
Version 3.2

For information about what's new in Optim pureQuery Runtime for Linux, UNIX, and Windows and Optim pureQuery Runtime for z/OS Version 3.1 releases, see http://www.ibm.com/support/docview.wss?uid=swg27022472.

Version 3.2

What's new in InfoSphere Optim pureQuery Runtime for Linux, UNIX, and Windows Version 3.2 and InfoSphere Optim pureQuery Runtime for z/OS Version 3.2

InfoSphere Optim pureQuery Runtime Version 3.2 provides key enhancements in the following categories:


SQL Management Repository

The following enhancements have been made for SQL Management repositories:

  • You can specify a schema when you create a repository in a database. With the pureQuery ManageRepository utility option -repositorySchema, you can specify a schema when creating a repository. The ability to specify a schema gives you more control when creating a repository and lets you create multiple repositories in a single database.

    To enable pureQuery Runtime to access a repository that was created with the option -repositorySchema, you specify the schema name with the pureQuery Runtime property pdq.repositorySchema.
  • You can specify that the pureQuery Runtime retrieve the information when a repository runtime group version is activated to more efficiently manage when pureQuery Runtime retrieves pureQuery information from a repository.

    The pureQuery Runtime property pdq.runtimeGroupActivationCheckInterval controls the activation-based refresh of pureQuery information for all active repository runtimeGroup versions. The property propertiesRefreshInterval controls the refresh for specific active repository runtimeGroup versions.

Link to related information:


Management of SQL statements

The following enhancements have been made for the management of SQL statements:

  • You can retrieve SQL statements from a dynamic cache of a DB2 for z/OS subsystem with the pureQuery GeneratePureQueryXml utility. Retrieving statements from a dynamic cache simplifies the pureQuery client optimization process for applications that access data from DB2 for z/OS databases
  • You can use the StaticBinder utility options -singletonSelect and -commentOnPackage to manage SQL statements:
    • With the option -singletonSelect, the StaticBinder utility optimizes SQL queries that access a single table and that return at most one row.
    • With the option -commentOnPackage, you can specify the package-comment text in the catalog descriptions of the DB2 packages when the StaticBinder utility creates a package.

Link to related information:



WebSphere Application Sever support

The following enhancements support pureQuery enabled applications in a WebSphere Application Server environment:

  • You can configure an IBM WebSphere application server with pureQuery Runtime and validate the configuration. The pureQuery Runtime for Linux, UNIX, and Windows installation contains scripts to install pureQuery Runtime on an IBM WebSphere application server.The installation also contains scripts and a servlet application that validates the pureQuery installation.
  • You can specify the JNDI variables ${appName} and ${moduleName} in a pureQuery Runtime properties file. pureQuery Runtime supports the JNDI variables in a WebSphere Application Server environment.. To simplify the deployment of pureQuery enabled applications, you can specify the JNDI variables in an application-level scope pureQuery Runtime properties file and create a single generic file. The single file can replace a set of files that contain application specific values in each file.

Link to related information:



Batch heterogenous update exception handling

The following enhancement has been made to batch heterogeneous update exception handling:

  • You can use com.ibm.pdq.runtime.exception.HeteroBatchSQLException to easily retrieve exception information for updates performed by batch heterogenous updates, HeteroBatchSQLException contains SQL error information for batch Batch heterogenous update . You can retrieve a two-dimensional int array that contains the update count for the batch heterogeneous update by calling UpdateManyException.getUpdateCounts() method.

Link to related information:


pureQuery Runtime overview information

To quickly learn about the pureQuery Runtime technology, the pureQuery overview and introduction have been enhanced and expanded.

Link to related information:

Cross reference information
Segment Product Component Platform Version Edition
Information Management InfoSphere Optim pureQuery Runtime for z/OS z/OS 3.2

Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Optim pureQuery Runtime for Linux, UNIX and Windows

Software version:

3.2

Operating system(s):

AIX, HP-UX, Linux, Linux pSeries, Linux zSeries, Solaris, Windows

Reference #:

7036141

Modified date:

2012-12-07

Translate my page

Machine Translation

Content navigation