ODBC/MX Driver for Windows Manual for SQL/MX Release 3.2 (H06.25+, J06.14+)
HP NonStop ODBC/MX Driver for Windows—691126-003
4-1
4 Module File Caching (MFC)
MFC Overview
Before the H06.18/J06.07 RVU, the ODBC/MX driver did not cache the NonStop
SQL/MX prepared statements. As a result, applications recompiled the same SQL/MX
statements, causing higher host processor and memory utilization, which lead to poor
performance.
The Module File Caching (MFC) feature shares the SQL/MX prepared statement plans
among the SQL/MX database connections. It helps in reducing the SQL/MX
compilation time during the steady state of the ODBC application, thereby reducing
resource consumption.
MFC Design
For information on the MFC design, see the HP NonStop SQL/MX Connectivity Service
Manual.
Configuring MFC
For information on configuring MFC, see the HP NonStop SQL/MX Connectivity
Service Manual.
MFC Overview 4-1
MFC Design 4-1
Configuring MFC 4-1
MFC Usage Scenarios 4-2
MFC Limitations 4-2
Troubleshooting MFC 4-2
Note. MFC is supported only on systems running J06.07 and later J-series RVUs and H06.18
and later H-series RVUs. Starting with SQL/MX Release 3.2, MFC supports the BigNum data
type in parameterized queries.
Note. The SSL ODBC/MX and MXOAS processes must run on the same TCP/IP process. Tar-
getPort may not be specified with HP NonStop SSL SETUP macro.










