MX Release 3.1 (H06.23+, J06.12+)

Starting, Configuring, and Managing MXCS

HP NonStop SQL/MX Connectivity Service Manual for SQL/MX Release 3.1—663856-001

3-35

Benefits of MFC

JDBC and ODBC applications that use complex queries result in lower processor

utilization, lower memory consumption, and better response time.

Limitations of MFC

•

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

SQL/MX Control Query Shape (CQS).

•

For light weight queries, MFC performs only marginally better than SQL/MX

compile.

•

MFC is not supported for rowset operations.

•

Starting with SQL/MX 3.1, MFC supports only INSERT, SELECT, UPDATE, or

DELETE queries.

Troubleshooting MFC

The troubleshooting of MFC includes:

•

.err Files

•

.lock Files

•

.mdf Files

•

.lst Files

•

.sql Files

•

Disk Activity

•

Enable Fileset and OSS Caching

•

Known Issues

.err Files

The *.err files are intermediate files available at a location specified in

COMPILED_MODULE_LOCATION EVAR, which reports MXCMP errors, if any,

generated during module file creation.

If MXCMP passes successfully, the *.err files are removed automatically after the

module file is created. Otherwise, the *.err files are stored at the specified location for

further analysis of the reported failure.

.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. The *.lock files are deleted from the