MX Release 3.2 (H06.25+, J06.14+)

The mgscript is located at the Guardian location, where the MXOSRVR objects are present. The

following options can be used with the MFC management script:

This option deletes all MFC related files from the specified

directory. For example:

-A

>>mgscript -A <Dir>

Dir : This must be the directory mentioned

in the compiled_module_location

This option deletes all MFC related binary files from the

specified directory related to a specific table. For

example:

-T

>>mgscript –T <Dir> <table_name>

<catalog_name.schema_name>

-T must have three options: Directory, table name, and

catalog.schema name.

When you alter the table using MXCI, specify the correct

table name. Do not use wild card characters.

This option deletes all MFC related files from the

specified directory related to a specific catalog and

schema. For example:

-C

>>mgscript –C <Dir> <catalog_name>

<schema_name>

-C must have three options: Directory, catalog name, and

schema name.

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” (page 52)

• “.lock Files” (page 52)

• “.mdf Files” (page 52)

• “.lst Files” (page 52)

• “.sql Files” (page 52)

• “Disk Activity” (page 53)

• “Enable Fileset and OSS Caching” (page 53)

• “Known Issues” (page 54)

Module File Caching (MFC) 51