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

NOTE:

• If you specify the compiled_module_location evar to a value other than the

default, such as /usr/temp, ensure that the directory is created before specifying it.

• While upgrading the SQL/MX Release 2.3.x to SQL/MX Release 3.2, delete all the

MFC files that were created at the default location or

compiled_module_location.

6. To verify that the values are assigned, enter the following command:

CS>info evar <data source>.*, type set;

The following output appears indicating that the values are assigned:

-- INFO EVAR \DMR15.$VCD9.<data source>.* Report

Sets:

SET STATEMENT_MODULE_CACHING TRUE

SET COMPILED_MODULE_LOCATION default

7. By default, MFC is disabled for SQLExecDirect. However, when you enable MFC for an

application as described from Step 1 to Step 6 of this procedure, MFC for SQLExecDirect

with parameterized queries is enabled and module files are created. To enable MFC for

SQLExecDirect non parameterized queries, configure the following setting:

add evar $R32.RAZ32_MFC.STATEMENT_EXECDIRECT_CACHING, type set, value 'true';

8. Start the data source:

start ds $MXOAS.”MCBS_datasource”;

Configuring MFC using NSM/Web

To configure MFC using NSM/Web:

1. Log on to NSM/Web.

2. Click MXCS.

3. Under Data Source Configurations, click the data source name for which you want to enable

MFC.

4. Click Sets.

5. To set the statement module caching:

a. Click +.

b. In the Name field, enter statement_module_caching.

c. In the Value field, enter true.

d. Click OK.

6. To add the compiled module location:

a. Click +.

b. In the Name field, enter compiled_module_location.

c. In the Value field, enter default or any other location that you want.

d. Click OK.

7. Click Apply.

8. Stop and start the data source.

Managing MFC

Every application must have its own module file directory so that all the modules for an application

are grouped together.

OSS commands can be used to remove temporary files and modules when required.

The MFC module files can be managed using an OSS script called mgscript.

50 Starting, Configuring, and Managing MXCS