MX 2.x)

Starting, Configuring, and Managing MXCS

HP NonStop SQL/MX Connectivity Service Manual—524944-008

3-31

Troubleshooting MFC

.mdf Files

The .mdf temporary files are generated during preprocessing. These .mdf files are

retained for easier support and troubleshooting.

The preprocessor creates an SQL module definition file in the

<compiled_module_location> location that contains the embedded SQL

statements.

.lst Files

The .lst files are the output of the SQL/MX C/C++ preprocessor. In rare cases, these

files might contain compiler errors.

.sql Files

The .sql files contain the generated source code of the statement. This file is read by

the mxsqlc preprocessor to produce the .mdf file. The .sql files can be used to tune an

SQL statement by adding statement-specific Control Query Default and/or shapes.

Disk Activity

The MFC access plans are stored in the disk OSH location as specified in the attribute

compiled_module_location. For more information on setting this attribute, see

Configuring MFC on page 3-27. Assume that the value for the attribute is

/usr/mymodules. If specifying this location attribute causes an increase in the

processor utilization of disks, then to overcome this problem, use the fileset setting for

that directory. It is beneficial to have OSS caching enabled on data volumes. To enable

fileset and OSS caching, see Enable Fileset and OSS Caching on page 3-31.

Enable Fileset and OSS Caching

To add a fileset pointing to a value in the compiled_module_location directory,

complete the following steps:

1. At a TACL prompt, enter:

SCF

and then enter:

assume $zpmon

Note. For more information on module definition files, see the HP NonStop SQL/MX

Programming Manual for C and COBOL.

Note. If the table is altered using data definition language (DDL), it is recommended that you

run the management script (mgscript) to delete module files associated with that table or

catalog. For information on management script, see Managing MFC