JDBC Type 2 Driver 3.0 Programmer's Reference (SQL/MX 3.x)

Module File Caching (MFC)

The Module File Caching (MFC) feature shares the SQL/MX prepared statement plans among the JDBC/MX

T2 database connections and JVM processes. It helps in reducing the SQL/MX compilation time during the

steady state of the JDBC/MX T2 application, thereby reducing resource consumption.

Note: Module File Caching is supported only on systems running J06.07 and later J-series RVUs

and H06.18 and later H-series RVUs.

The topics discussed in this chapter are:

Design of MFC

Enabling MFC

Limitations of MFC

Troubleshooting MFC

Design of MFC

For information on the MFC design, see the

HP NonStop SQL/MX Connectivity Service Manual

Enabling MFC

The following are the two new properties which are required for using MFC in an application that uses the

JDBC/MX T2 Driver.

enableMFC Property:

To enable MFC, the value of this property must be set to ON.

compiledModuleLocation Property:

The value for this property must be a valid directory name. For example:

/usr/temp. This is the

location where the intermediary files such as

*.mdf for MFC are generated.

Both these properties must be set to enable MFC.

Limitations of MFC

MFC cache should be used only on production systems. It should not be used on development or User

Acceptance Testing (UAT) systems where SQL/MX undergoes changes.

It does not handle session-specific SQL/MX Control Query Defaults (CQD) and SQL/MX Control Query

Shape (CQS).