MX 2.x)

Starting, Configuring, and Managing MXCS

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

3-29

Managing MFC

2. Temporary files such as *.lst,*.sql*.mdf ; all these files are retained in the

directory to enable easy troubleshooting.

1. Start the data source:

start ds $MXOAS.”MCBS_datasource”;

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.

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:

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.

-A This option deletes all MFC related files from the specified

directory. For example:

>>mgscript -A <Dir>

Dir : This must be the directory mentioned in

the compiled_module_location

-T This option deletes all MFC related binary files from the

specified directory related to a specific table. For example:

>>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.

-C This option deletes all MFC related binary files from the

specified directory related to a specific catalog and schema.

For example:

>>mgscript –C <Dir> <catalog_name>

<schema_name>

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

schema name.