MX 2.x)

Starting, Configuring, and Managing MXCS

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

3-18

Tracing Server Activity

Session ID

Function Name

Sequence Number

Function information

Every trace event generates a pair of messages. The first message is written on entry

to a function, and contains the input parameters to the function. The second is written

on exit, and contains the exit parameters for the function. See Example Server Trace

Log for the Connect Function on page 3-20.

For detailed definitions of server trace fields that are collected, see the MXCS online

help, which is available on NSM/web.

For information on configuring server trace, see Configuring Server Tracing on

page 3-18.

Configuring Server Tracing

You must use a user ID that has OPERATOR permission to perform management

tasks.

1. Configure an alternate collector, using the EMSACOLL command. For details on

the EMSACOLL command, see the EMS Manual.

2. Start the alternate collector before starting the ODBC/MX service.

3. Use the MXOAS command to start the ODBC/MX service, and pass the name of

the alternate collector to the server in the -TMC parameter.

See Starting Server Tracing on page 3-18.

Starting Server Tracing

1. Do one of the following:

a. Using NSM/web click MXCS Services.

b. Expand MXCS Services and click a service name.

2. Click the Data Source Status tab.

3. Check the Tracing column for the data sources you want to trace.

4. When finished, click Apply.

Tracing starts for all available servers and connected servers.

For more information about a screen, click Help.

Note. If you stop an association server from TACL, the Enable Trace option is not retained for

a data source that is tracing server activity. When the association server is restarted, you must

enable tracing again.