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

Trace Event Message Format

Message 21034

MXCS Trace:

Session ID: session-id

Function: Enterfunction

Sequence Number: sequence-number

function-input-parameters

Session ID: session-id

Function: Exitfunction

Sequence Number: sequence-number

function-exit-parameters

session-id

unique session ID generated by the MXCS SQL server at the time the connection is

established.

function

The MXCS SQL server function that is being traced.

sequence number

Messages too large for one message template are divided into smaller messages.

Sequence number indicates which part of the message you are viewing. The

sequence number is 0 for the first or only part of a message, and 1 for the additional

parts, if any.

function-input-parameters

list of input parameters to the function.

function-exit-parameters

list of output parameters from the function.

Cause. A trace informational message.

Effect. None.

Informational message only, no corrective action is needed.

Module File Caching (MFC)

Prior to H06.18/J06.07 RVU, the ODBC/MX driver did not cache the NonStop SQL/MX prepared

statements. As a result, applications recompiled the same SQL/MX statements, causing higher host

utilization, which could lead to worse perceived performance of the ODBC client application.

The Module File Caching (MFC) feature shares the SQL/MX prepared statement plans among the

SQL/MX database connections. It helps in reducing the SQL/MX compilation time during the

steady state of the JDBC or ODBC application, thereby reducing resource consumption.

The MFC feature is supported by the JDBC Type 4 driver and ODBC/MX driver for Windows.

Starting with SQL/MX Release 3.2, MFC supports parameterized queries with BIGNUM data type.

For information on the JDBC Type 4 driver support for MFC, see the HP NonStop JDBC Type 4

Driver Programmer's Reference for SQL/MX Release 3.2.

For information on the ODBC/MX driver support for MFC, see the HP NonStop ODBC/MX Driver

for Windows for SQL/MX Release 3.2.

48 Starting, Configuring, and Managing MXCS