JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.1 (H06.23+, J06.12+)

It is recommended to set the CQD in SQL/MX for disabling the auto-recompilation feature of the
SQL/MX while using with MFC. This ensures that automatic recompilations are avoided due to changes
in SQL/MX objects because the plans are generated in the module file. The application will receive an
SQL/MX exception if there is an auto-recompilation required for the query. You must clean the stale
module files before continuing with the application.
For lightweight queries, MFC performs only marginally better than the SQL/MX compile.
Combining external statement cache with MFC does not yield memory benefits. The WebLogic Server
(WLS) statement cache is an example of external statement cache. It is recommended that you use
the JDBC/MX T2 statement cache.
Some scalar functions such as ABS, SUM, and AVG are not handled through the MFC in the first
release. For information on the scalar functions, see the
HP NonStop SQL/MX Reference Manual .
Troubleshooting MFC
The troubleshooting of MFC includes:
Benefits of MFC
Setting an Environment for MFC
.lock Files
.mdf Files
Disk Activity
Enable Fileset and OSS Caching
Known Issues
Benefits of MFC
JDBC applications using the java.sql.PreparedStatement object result in lower processor utilization, lower
memory consumption, and better response time.
Setting an Environment for MFC
See EnablingMFC.
.lock Files
The *.lock files are generated for every query that pass through the MFC module file creation process. These files are
also used for synchronizing, so that different connections do not re-create the same module file. These *.lock files are
deleted once the binary module in the /usr/tandem/sqlmx/USERMODULES directory is created successfully.
The *.lock files are not deleted for the queries that cannot create module files.
.mdf Files