MX 2.x)

Overview of MXCS

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

1-8

Errors, Events, and Warnings

All exceptions that occur during the MXCS service are written to the Event

Management Service (EMS) operator collector $0 or to the alternate EMS collector if

you configured it when you started the MXCS service. You can also configure the level

of detailed information sent to the collector, ranging from critical commands only to

verbose execution (which includes all internal status changes).

Event and error messages are described in the Operator Messages Manual.

Traces

You can trace activity for MXCS SQL servers.

Data collected on the server side:

•

Calls to entry functions and input values received

•

Calls to exit functions and output values returned

For detailed information about Server traces, see Tracing Server Activity on page 3-17.

Resource Statistics

The MXCS Resource Statistics facility collects statistics for use in estimating resource

usage and predicting resource cost. When statistics collection is turned on, collection

starts when the client connects to MXCS Server; thereafter, compilation and execution

of SQL statements are recorded. Data is recorded until the end of a user session, or

until you stop statistics collecting.

If the MXCS service is stopped, or if you stop a data source that has statistics

collecting started, the statistics options are retained. Therefore, when the data source

is restarted, statistics collection automatically resumes.

MXCS collects two categories of statistics:

•

Session statistics are typically used if the data is used for charge-back. Session

statistics report:

MXCS Permission Access

USER View status and configuration of MXCS services, data sources,

and server.

View permissions.

OPERATOR Enable, disable, manage, and configure MXCS.

View permissions.