Chapter 66 ODBC/MX Messages

The messages in this chapter are generated by the HP NonStop ODBC/MX subsystem. The subsystem ID displayed by these messages includes ODBCMX as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

20002

An unexpected programming exception <detail-text> has occurred. Event Type: event-type Component Name: component-name Object Reference: object-reference

`detail-text`	indicates additional detail that describes the event.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An error has occurred in the MXCS program.

Effect The operation fails, and the current transaction is rolled back. The current session might not be valid.

Recovery Check the Event log for the error(s) that occurred. Correct the reported error conditions and retry.

20004

A SQL/MX query failed. SQLCODE: sqlcode. Event Type: event-type Reporting Component: component Object Reference: object-reference Origin Component: component Detail Text: detail-text

`sqlcode`	indicates an HP NonStop SQL/MX error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.
`detail-text`	indicates additional detail that describes the event.

Cause An SQL/MX error occurred in a query submitted by MXCS.

Effect The current statement fails, and the current transaction is rolled back. The current session might not be valid.

Recovery Determine the sqlcode from the SQL/MX messages log, and then see the SQL/MX Messages Manual for a description of the error and recovery information.

20005

A network component error error-code has occurred. CEE Error Text: error-text Event Type: event-type Component Name: component-name Object Reference: object-reference

`error-code`	indicates the network component error number returned by MXCS.
`error-text`	is the message text that describes the network component error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component-name`	indicates the name of the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An error occurred in the transport layer.

Effect MXCS will not start or, if the error occurs during a session, an error code is generated by the transport layer.

Recovery If you cannot start MXCS, check the Event log for errors that occurred. Correct the reported error conditions and retry. If this error occurs during a session, close the current server session and open a new one.

20006

SQL/MX Server failed to register back to MX Connectivity Service. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An SQL/MX server failed to register with the SQL/MX connectivity service.

Effect The SQL/MX server terminates.

Recovery Check the Event log for errors that occurred. Correct the reported error conditions and retry.

20007

A NonStop Process Service error process-services-error has occurred. Event Type: event-type Component: component Object Reference: object-reference

`process-services-error`	indicates a file-system error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An error occurred in the NonStop Process Services, which is the component that includes the message system, process control facilities, and timing facilities for SQL/MX on a system.

Effect The effect depends on the error.

Recovery See Appendix B, for a definition of the specified error. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.

20008

MX Connectivity Service starting parameters: parameters. Event Type: event-type Component: component Object Reference: object-reference

`parameters`	indicates the parameters specified when starting the SQL/MX connectivity service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service is starting and is reporting its initial parameters.

Effect None.

Recovery Informational message only; no corrective action is needed.

20009

Memory allocation error in the function: function-name Event Type: event-type Component: component Object Reference: object-reference

`function-name`	indicates the name of the function in which the error occurred.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A memory allocation error occurred in the specified function.

Effect The component indicated in the message might not be able to continue. When reported as a warning, the component continues processing in some limited capacity. When reported as an error, the component terminates.

Recovery Free up additional memory or swap space, or both, by stopping applications or processes you do not require.

20010

A SQL/MX warning sql-state has occurred. Event Type: event-type Reporting Component: component Object Reference: object-reference Origin Component: component Detail Text: detail-text

`sql-state`	indicates a SQL/MX warning.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.
`detail-text`	indicates additional detail that describes the event.

Cause An SQL/MX warning occurred.

Effect The effect depends on the SQL/MX warning.

Recovery Determine the sql-state from the SQL/MX messages log, and then see the SQL/MX Messages Manual for a description of the error and recovery information.

20011

An error error has occurred while setting the attribute attribute-name with value attribute-value for Define define-name. Event Type: event-type Component: component Object Reference: object-reference

`error`	indicates the error code returned by he Guardian procedure DEFINESETATTR. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`attribute-name`	indicates the class attribute of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`attribute-value`	indicates the value of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`define-name`	indicates the name of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Guardian error occurred due to an invalid define name, attribute name, or attribute value.

Effect The SQL/MX server process does not inherit the define set.

Recovery Determine the error from the MXCS messages log, and then supply the correct values.

20012

A define error error has occurred while saving the Define define-name. Event Type: event-type Component: component Object Reference: object-reference

`error`	indicates the error code returned by the Guardian procedure DEFINESAVE. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`define-name`	indicates the name of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Guardian error has occurred.

Effect The SQL/MX server process does not inherit the define set.

Recovery Determine the error from the MXCS messages log, and then see the Guardian Procedures Calls Reference Manualfor a description of the error and recovery information.

20400

Resource Policy exceeds limit. Estimated cost: estimated-cost Limit cost: limit-cost SQL Text: SQL/MX-query Event Type: event-type Component Name: component Client ID: client-identifier Object Reference: object-reference

`estimated-cost`	indicates the cost of the query expressed as a nonnegative number.
`limit-cost`	indicates the maximum value allowed for the query cost expressed as a nonnegative number.
`SQL/MX-query`	is the SQL/MX query.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`client-identifier`	indicates the ODBC/MX client that made the query.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A resource governing policy exceeded the maximum allowed for the specified SQL/MX query.

Effect If the action is STOP, the query is aborted; otherwise, there is no effect.

Recovery Informational message only; no corrective action is needed.

20401

Query query estimated cost estimated-cost exceeds resource policy resource-policy. Query marked un-executable. Event Type: event-type Component: component Object Reference: object-reference

`query`	indicates the SQL/MX query.
`estimated-cost`	indicates the cost of the query expressed as a nonnegative number.
`resource-policy`	indicates the maximum value allowed for the query cost expressed as a nonnegative number.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The estimated cost of the SQL/MX query exceeds the cost limit set in the resource governing policy.

Effect The query is not executed.

Recovery Update the resource governing policy of the data source and reexecute the query.

20402

The monitor object call object-call to the MX Connectivity Service failed. Event Type: event-type Component: component Object Reference: object-reference

`object-call`	indicates that the call that failed.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A monitor object call to the specified object failed to register back to the SQL/MX connectivity service.

Effect The monitor object call fails.

Recovery Wait and retry the operation or verify whether the SQL/MX connectivity service is running.

20403

Failed to timeout while in idle state, due to an error in the object call to MX Connectivity Service or due to timer creation error. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An idle SQL/MX server failed to time out.

Effect The SQL/MX server continues to run.

Recovery Check whether the system is slow. If not, adjust the idle timeout value.

20404

SQL/MX Server failed to update its state in the MX Connectivity Service. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An SQL/MX server failed to update its state with the SQL/MX connectivity service.

Effect The state is not updated.

Recovery Stop the server. Verify if the SQL/MX connectivity service is available, and then retry.

20423

ODBC/MX client fails to connect due to error error in setting up the connection context. Event Type: event-type Component: component Object Reference: object-reference

`error`	indicates a ODBC/MX connection context error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX client failed to connect to an SQL/MX server because of an SQL error.

Effect The ODBC/MX client is not connected, and the server is stopped.

Recovery Correct the SQL problem, and then retry.

20950

MXCS Configuration Server is initialized. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The MXCS configuration server has completed initialization.

Effect The configuration server is initialized.

Recovery Informational message only; no corrective action is needed.

21000

SQL/MX Server failed to register. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the SQL/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX server is unable to register back to the SQL/MX connectivity service because of a network error on an HP NonStop server.

Effect The SQL/MX server is not registered.

Recovery Correct the network problem. Stop the SQL/MX connectivity service and then restart it.

21001

SQL/MX Server changed state from previous-state to current-state. Event Type: event-type Component: component Object Reference: object-reference Server Object Reference:server-object-reference

`previous-state`	indicates the state of the SQL/MX connectivity service before the event occurred.
`current-state`	indicates the current state of the SQL/MX connectivity service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.
`server-object-reference`	indicates the name of the server object in which the event occurred.

Cause An internal error occurred in the SQL/MX connectivity service.

Effect The server is disabled.

Recovery Identify and stop the problem server.

21002

Start SQL/MX server server-type failed on port port-number. Event Type: event-type Component: component Object Reference: object-reference

`server-type`	is one of: AS_SERVER (the association server) CFG_SRVR (the configuration server) CORE_SRVR (the SQL/MX server)
`port-number`	indicates the number of the port that failed.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The spawn process failed.

Effect The SQL/MX server is not started.

Recovery Check for server and file-system problems and correct them.

21003

Stop SQL/MX server failed on port port-number. Event Type: event-type Component: component Object Reference: object-reference

`port-number`	indicates the number of the port that failed.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service could not stop an SQL/MX server because of a previous error.

Effect The SQL/MX server is not stopped.

Recovery Check the MXCS event log for the previous error.

21005

MXCS data source data-source changed state from previous-state to current-state. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of the data source.
`previous-state`	indicates the state of the SQL/MX connectivity service before the event occurred.
`current-state`	indicates the current state of the SQL/MX connectivity service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An internal error occurred for the specified MXCS data source during a state change.

Effect The MXCS data source might not be available for use by client applications.

Recovery Restart the MXCS data source. Report this problem to your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable.

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.

21006

No more ports available to start SQL/MX servers. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause All ports configured for SQL/MX servers are in use, and the SQL/MX connectivity service cannot start any more servers.

Effect The SQL/MX server is not started.

Recovery The SQL/MX server cannot start until a port is available. Use the NonStop Software Manager to determine the status of SQL/MX servers. To free up additional ports, disconnect unused MXCS clients and stop idle SQL/MX servers.

21007

MX Connectivity Service is started. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service is started.

Effect None.

Recovery Informational message only; no corrective action is needed.

21008

The MXCS data source data-source is started. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service has started the specified data source.

Effect None.

Recovery Informational message only; no corrective action is needed.

21009

MX Connectivity Service failed to start due to the previous error(s). Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service failed to start because of one or more errors.

Effect The SQL/MX connectivity service is not started.

Recovery Check the MXCS event log for the error(s) that occurred.

21010

MX Connectivity Service started with some information. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service was able to spawn processes but with problems.

Effect The SQL/MX connectivity service is started.

Recovery Check the MXCS event log for the previous error(s) that occurred.

21011

Start MXCS data source data-source failed. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The specified MXCS data source failed to start because of one or more errors.

Effect The MXCS data source is not started.

Recovery Check the MXCS event log for the previous error(s) that occurred.

21012

The MXCS data source data-source started with some information. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The specified MXCS data source is started with some warnings.

Effect The specified MXCS data source is started.

Recovery Check the MXCS event log for the previous error(s) that occurred.

21013

MX Connectivity Service is stopped. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the SQL/MX connectivity service.

Effect The SQL/MX connectivity service is stopped.

Recovery Informational message only; no corrective action is needed. To use MXCS again, you must restart it.

21014

The MXCS data source data-source is stopped for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the specified MXCS data source.

Effect The MXCS data source is stopped and is not available for client connections.

Recovery Informational message only; no corrective action is needed.

21015

MX Connectivity Service stopped with some failure(s). See previous event(s). Event Type: event-type Component: component-name Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component-name`	indicates the SQL/MX connectivity service (MXCS) component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the SQL/MX connectivity service, and some failures occurred.

Effect The SQL/MX connectivity service is stopped.

Recovery Check the MXCS event log for the previous error(s) that occurred.

21016

The MXCS data source data-source stopped for reason with some information. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the specified MXCS data source, and some warnings occurred.

Effect The MXCS data source is stopped.

Recovery Check the MXCS event log for the previous error(s) that occurred.

21017

Setting the initial SQL/MX server context failed. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service could not set the initial context for the SQL/MX server.

Effect The SQL/MX server is not usable for client connections.

Recovery Stop the SQL/MX server, and then correct the problem and retry.

21019

SQL/MX server srvr-obj-ref changing state from previous-state to current-state. Event Type: event-type Component: component Object Reference: object-reference

`srvr-obj-ref`	indicates the SQL/MX server whose state is changing.
`previous-state`	indicates the state of the SQL/MX connectivity service before the event occurred.
`current-state`	indicates the current state of the SQL/MX connectivity service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The state of the SQL/MX server has changed.

Effect The SQL/MX server is in the new state specified.

Recovery Informational message only; no corrective action is needed.

21020

The MXCS data source data-source is stopping for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The Stop option was issued for the specified MXCS data source.

Effect The data source is in the process of stopping and is not available for client connections.

Recovery Informational message only; no corrective action is needed.

21021

The MXCS data source data-source is stopped abruptly for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Stop Abrupt option was issued for the specified MXCS data source.

Effect The data source is stopped and is not available for client connections. The Stop Abrupt option stops a data source immediately, without waiting for its associated SQL/MX servers to finish current SQL/MX statements or sessions. The Transaction Manager tries to roll back outstanding transactions. However, the database might be left in an inconsistent state.

Recovery Informational message only; no corrective action is needed.

21022

The MXCS data source data-source stopped abruptly for reason with some information. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The specified MXCS data source was stopped abruptly with the Stop Abrupt option, and some failures occurred.

Recovery Check the MXCS events in the application log for the previous error(s) that occurred.

21023

The MXCS data source data-source is stopping abruptly for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The Stop Abrupt option was issued for the specified MXCS data source.

Effect The data source is in the process of stopping abruptly and is not available for client connections.

Recovery Informational message only; no corrective action is needed.

21024

The MXCS data source data-source is stopping in Stop-When-Disconnected mode for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The Stop option, with the Stop When Disconnected mode, was issued for the specified MXCS data source.

Effect The data source is not stopped until all clients have disconnected. The data source rejects new connection requests.

Recovery Informational message only; no corrective action is needed.

21025

MX Connectivity Service is stopped abruptly for reason. Event Type: event-type Component: component Object Reference: object-reference

`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Stop Abrupt option was issued for the SQL/MX connectivity service.

Effect The SQL/MX connectivity service is in the process of stopping.

Recovery Informational message only; no corrective action is needed.

21026

MX Connectivity Service started with warning warning-text from configuration server. Event Type: event-type Component: component Object Reference: object-reference

`warning-text`	indicates the warning message returned by the configuration server.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service was started, but the MXCS configuration server returned a warning.

Effect The SQL/MX connectivity service is started.

Recovery Correct the problem indicated in the warning.

21028

SQL/MX has not successfully completed its initialization. MX Connectivity Services cannot be started. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A start request was sent to the SQL/MX connectivity service, but the SQL/MX initialization, which includes the MXCS initialization, has not completed.

Effect The SQL/MX connectivity service is not started.

Recovery Wait for the SQL/MX and MXCS initialization to complete, and then start the SQL/MX connectivity service.

21029

MX Connectivity Service initialized. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service has finished initialization.

Effect Initialization for the SQL/MX connectivity service is complete.

Recovery Informational message only; no corrective action is needed.

21030

MX Connectivity Service failed to save data source data-source status status. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`status`	indicates the status that could not be saved for the data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service could not save a status change for the indicated data source because of one or more errors.

Effect The MXCS data source status change is not saved.

Recovery Check the application log for the errors that occurred, which most often are SQL/MX or network component errors. Correct the problem.

21031

MX Connectivity Service failed to save status status of MX Connectivity Service. Event Type: event-type Component: component Object Reference: object-reference

`status`	indicates the status that could not be saved for the SQL/MX connectivity service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The SQL/MX connectivity service could not save a status change because of one or more errors.

Effect The SQL/MX connectivity service status change is not saved.

Recovery Check the application log the errors that occurred, which most often are SQL/MX or network component errors. Correct the problem.

21033

SQL/MX server failed to write to collector collector due to error errnum. Session ID: session-id Component Name: MX Connectivity Service Object Reference: object-reference Error Message: error-message Collector Name: alternate-collector-name

`collector`	indicates the type of collector, MXCS server trace or resource statistics.
`errnum`	indicates a file system error.
`session-id`	indicates the unique session ID generated by the SQL/MX server at the time the connection is established.
`object-reference`	indicates the reference of the object in which the event occurred.
`error-message`	is text explaining the error encountered.
`alternate-collector-name`	is the name of the alternate collector started for resource statistics or server trace.

Cause An alternate collector, specified in the MXOAS command for resource statistics or server trace, is not running, or the name is invalid.

Effect SQL/MX server cannot write to the named collector.

Recovery If the alternate collector is not running, stop and start another trace or statistics collector. If the collector name specified in the MXOAS command is invalid, stop the SQL/MX connectivity service, and then reissue the MXOAS command with a valid collector name.

21034

MXCS Trace: Session ID: session-id Function: Enterfunction Sequence Number: sequence-number function-input-parameters OR Session ID: session-id Function: Exitfunction Sequence Number: sequence-number function-exit-parameters

`session-id`	indicates the unique session ID generated by the SQL/MX server at the time the connection is established.
`function`	indicates the SQL/MX server function that is being traced.
`sequence-number`	indicates which part of the message you are viewing. Messages too large for one message template are divided into smaller messages. The sequence number is 0 for the first or only part of a message and 1 for additional parts, if any.
`function-input-parameters`	is the list of input parameters to the function.
`function-exit-parameters`	is the list of output parameters from the function.

Cause A trace informational message was issued.

Effect None.

Recovery Informational message only, no corrective action is needed.

21035

MXCS Statistics: Session ID: session-id Message Attribute: message-attribute Sequence Number:sequence-number Message Info:statistics-information message-attribute is: { SESSION:ConnectionInformation } { SESSION: SessionSummary } { STATEMENT: SQLStatement } { STATEMENT: SQLExecDirect } { STATEMENT: SQLExecute } { STATEMENT: SQLPrepare } { STATEMENT: SQLFetch }

`session-id`	indicates the unique session ID generated by the SQL/MX server at the time the connection is established.
`message-attribute`	indicates the name of the statistics option you selected.
`sequence-number`	indicates which part of the message you are viewing. Messages too large for one message template are divided into smaller messages. The sequence number is 0 for the first or only part of a message and 1 for additional parts, if any.
`statistics-information`	indicates the statistics collected for the session or statement options selected.

Cause A resource statistics informational message was issued.

Effect None.

Recovery Informational message only; no corrective action is needed.

21036

MXCS Query Status: Session ID: session-id Message Attribute: message-attribute Sequence Number: sequence-number Message Info: query-status-information message-attribute is: { STATEMENT:START:QueryExecution } { STATEMET:END:QueryExecution }

`session-id`	indicates the unique session ID generated by the SQL/MX server at the time the connection is established.
`message-attribute`	indicates the start or end of the query execution.
`sequence-number`	indicates which part of the message you are viewing. Messages too large for one message template are divided into smaller messages. The sequence number is 0 for the first or only part of a message and increases for additional parts, if any.
`query-status-information`	indicates the query status and information.

Cause Query execution is started or ended.

Effect None.

Recovery Informational message only; no corrective action is needed.

21260

The user has insufficient privileges to start MX Connectivity Service. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the MXCS component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause You attempted to start the SQL/MX connectivity service with insufficient privileges.

Effect The SQL/MX connectivity service is not started.

Recovery Ask the system administrator to grant the privileges to start the SQL/MX connectivity service.

30002

An unexpected programming exception <detail-text> has occurred. Event Type: event-type Component Name: component-name Object Reference: object-reference

`detail-text`	indicates additional detail that describes the event.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An error has occurred in the ODBC/MX program.

Effect The operation fails, and the current transaction is rolled back. The current session might not be valid.

Recovery Check the Event log for the error(s) that occurred. Correct the reported error conditions and retry.

30004

A SQL/MX query failed. SQLCODE: sqlcode. Event Type: event-type Reporting Component: component Object Reference: object-reference Origin Component: component Detail Text: detail-text

`sqlcode`	indicates a SQL/MX error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.
`detail-text`	indicates additional detail that describes the event.

Cause An SQL/MX error occurred in a query submitted by ODBC/MX.

Effect The current statement fails, and the current transaction is rolled back. The current session might not be valid.

Recovery Determine the sqlcode from the SQL/MX messages log, and then see the SQL/MX Messages Manual for a description of the error and recovery information.

30005

A network component error error-code has occurred. CEE Error Text: error-text Event Type: event-type Component Name: component-name Object Reference: object-reference

`error-code`	indicates the network component error number returned by ODBC/MX.
`error-text`	is the message text that describes the network component error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An error occurred in the transport layer.

Effect ODBC/MX does not start or, if the error occurs during a session, an error code is generated by the transport layer.

Recovery If you cannot start ODBC/MX, check the Event log for the error(s) that occurred. Correct the reported error conditions and retry. If this error occurs during a session, close the current server session and open a new one.

Table 66-1 “Network Component Errors and Messages” lists the network component errors and their respective messages.

Table 66-1 Network Component Errors and Messages

Error	Error Message
-1	Unknown error
-2	Client failed
-3	Server failed
-4	Client unable to allocate resources
-5	Server unable to allocate resources
-6	Request too big
-7	Response too big
-8	Operation not defined for this interface
-9	Operation not implemented by server
-10	Invalid request header received
-11	Invalid response header received
-12	Unsupported request version
-13	Unsupported response version
-14	Request had unexpected length (too long)
-15	Response had unexpected length (too short)
-16	Request had unexpected length (too short)
-17	Response had unexpected length (too short)
-18	Request had invalid sequence size
-19	Response had invalid sequence size
-20	Request had invalid string size
-21	Response had invalid string size
-22	Invalid proxy object
-23	Call already outstanding on proxy
-24	Proxy no longer valid
-25	Disallowed synchronous call
-26	Proxy/interface mismatch
-27	Object does not exist
-28	Invalid object reference
-29	Transport failure
-30	Unimplemented conversion
0	Operation completed successfully
1	Unknown error
2	Memory allocation failure
3	Entity already exists
4	Invalid Handle
5	Proxy is no longer valid
6	CIN description of interface is invalid
7	Entity is in use
8	Invalid method index
9	Operation cannot be performed synchronously
10	Internal CEE inconsistency detected
11	Titanium OC error
12	Obsolete
13	Invalid object initialization function name
14	Invalid implementation library
15	Error unloading implementation library
16	Not all the configured objects were initialized
17	There is already a call outstanding on this proxy
18	Cannot mix synchronous and asynchronous implementations
19	Entity already destroyed
20	Unexpected client failure
21	Unexpected server failure
22	Invalid request header received
23	Invalid response header received
24	Version of received request is not supported
25	Version of received response is not supported
26	Request was unexpectedly long
27	Response was unexpectedly long
28	Request was unexpectedly short
29	Response was unexpectedly short
30	Request contained IDL sequence with invalid size
31	Response contained IDL sequence with invalid size
32	Request contained IDL string with invalid size
33	Response contained IDL string with invalid size
34	Interface does not define requested operation
35	Operation not implemented
36	Invalid time specified
37	Invalid parameter vector (proxy and call interfaces differ)
38	No such object
39	Invalid object reference
40	Invalid transport specified
41	Entity does not exist
42	Object ID is too large
43	Object is configured but not active
44	Invalid object ID
45	Maximum number of asynchronous I/Os exceeded
46	CEE_INITIALIZE not yet called
47	CEE_INITIALIZE has already been called
48	Memory not allocated by CEE
49	Error communicating with other capsule
50	Partner capsule closed connection
51	Partner capsule closed connection
52	CEE_EXECUTE has nothing more to do
53	Process is not named
54	Unable to log event
55	Invalid Event specified
56	Invalid file descriptor
57	Unexpected SKI error
58	Configuration record not found
59	Capsule name is too long
60	Capsule name has invalid syntax
61	Unused entry point
62	Object initialization function returned an error
63	Configured table size reached
64	Attempted to destroy a configured object
65	Object call was canceled
66	Invalid signal number
67	Maximum number of Titanium signal tags exceeded
68	Resultant request message is too large
69	Resultant response message is too large
70	Unimplemented data type conversion

30006

ODBC/MX Server failed to register back to ODBC/MX Service. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An ODBC/MX server failed to register with the ODBC/MX service.

Effect The ODBC/MX server terminates.

Recovery Check the Event log for the previous error(s) that occurred. Correct the reported error conditions and retry.

30007

A NonStop Process Service error process-services-error has occurred. Event Type: event-type Component: component Object Reference: object-reference

`process-services-error`	indicates a file-system error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An error occurred in the NonStop Process Services, which is the component that includes the message system, process control facilities, and timing facilities for SQL/MX on a system.

Effect The effect depends on the error that occurred.

Recovery See Appendix B, for a definition of the specified error. For more detailed information, including recovery actions, see the Guardian Procedure Errors and Messages Manual.

30008

ODBC/MX Service starting parameters: parameters. Event Type: event-type Component: component Object Reference: object-reference

`parameters`	indicates the parameters specified when starting the ODBC/MX service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service is starting and is reporting its initial parameters.

Effect None.

Recovery Informational message only; no corrective action is needed.

30009

Memory allocation error in the function: function-name Event Type: event-type Component: component Object Reference: object-reference

`function-name`	indicates the name of the function in which the error occurred.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A memory allocation error occurred in the specified function.

Recovery Free up additional memory or swap space, or both, by stopping unneeded applications or processes.

30010

A SQL/MX warning sql-state has occurred. Event Type: event-type Reporting Component: component Object Reference: object-reference Origin Component: component Detail Text: detail-text

`sql-state`	indicates a SQL/MX warning.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.
`detail-text`	indicates additional detail that describes the event.

Cause An SQL/MX warning occurred.

Effect The effect depends on the SQL/MX warning.

Recovery Determine the sql-state from the SQL/MX messages log then see the NonStop™ SQL/MX Messages Manual for a description of the error and recovery information.

30011

`error`	indicates the error code returned by the Guardian procedure DEFINESETATTR. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`attribute-name`	indicates the class attribute of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`attribute-value`	indicates the value of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`define-name`	indicates the name of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Guardian error occurred due to an invalid define name, attribute name, or attribute value.

Effect The ODBC/MX server process does not inherit the define set.

Recovery Determine the error from the ODBC/MX messages log, and then supply the correct values.

30012

A define error error has occurred while saving the Define define-name. Event Type: event-type Component: component Object Reference: object-reference

`error`	indicates the error code returned by the Guardian procedure DEFINESAVE. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`define-name`	indicates the name of the define. For more information, see the DEFINE Errors section in the Guardian Procedure Errors and Messages Manual.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that either reported the event or in which the event originally occurred.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Guardian error has occurred.

Effect The ODBC/MX server process does not inherit the define set.

Recovery Determine the error from the ODBC/MX messages log, and then see the Guardian Procedures Calls Reference Manualfor a description of the error and recovery information.

30400

Resource Policy policy-attribute limit limit-value exceeded. Action: action-value. Event Type (PID): event-type Component: component Client ID: client-identifier Object Reference: object-reference Observed Value: actual-value SQL Statement: sql-statement

`policy-attribute`	indicates a SQL/MX resource policy.
`limit-value`	indicates the maximum value allowed for the resource policy.
`action-value`	indicates the specified action value for the resource policy.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`client-identifier`	indicates the SQL/MX client that made the query.
`object-reference`	indicates the reference of the object in which the event occurred.
`actual-value`	indicates the resource policy value specified in the query.
`sql-statement`	indicates the SQL/MX statement in which the resource policy was specified in the query.

Cause A resource governing policy exceeded the maximum value allowed for the specified SQL/MX query.

Effect If the action is STOP, the query is aborted; otherwise, there is no effect.

Recovery Informational message only; no corrective action is needed.

30402

The monitor object call object-call to the ODBC/MX Service failed. Event Type: event-type Component: component Object Reference: object-reference

`object-call`	indicates that the call that failed.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A monitor object call to the specified object failed to register back to the ODBC/MX service.

Effect The monitor object call fails.

Recovery Wait and retry the operation, or verify whether the ODBC/MX service is running.

30403

Failed to timeout while in idle state, due to an error in the object call to ODBC/MX service or due to timer creation error. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An idle ODBC/MX server failed to time out.

Effect The ODBC/MX server continues to run.

Recovery Check whether the system is slow. If not, adjust the idle timeout value.

30404

ODBC/MX Server failed to update its state in the ODBC/MX Service. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An ODBC/MX server failed to update its state with the ODBC/MX service.

Effect The state is not updated.

Recovery Stop the server. Verify if the ODBC/MX service is available, and then retry.

30423

ODBC/MX client fails to connect due to error error in setting up the connection context. Event Type: event-type Component: component Object Reference: object-reference

`error`	indicates an SQL/MX connection context error.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX client failed to connect to an ODBC/MX server because of an SQL error.

Effect The ODBC/MX client is not connected and server is stopped.

Recovery Correct the SQL problem, and then retry.

30950

ODBC/MX Configuration Server is initialized. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX configuration server has completed initialization.

Effect None.

Recovery Informational message only; no corrective action is needed.

31000

ODBC/MX Server failed to register. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX server is unable to register back to the ODBC/MX service because of a network error on an HP NonStop server.

Effect The ODBC/MX server is not registered.

Recovery Correct the network problem. Stop the ODBC/MX service and then restart it.

31001

ODBC/MX Server changed state from previous-state to current-state. Event Type: event-type Component: component Object Reference: object-reference Server Object Reference: server-object-reference

`previous-state`	indicates the state of the ODBC/MX service before the event occurred.
`current-state`	indicates the current state of the ODBC/MX service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.
`server-object-reference`	indicates the name of the server object in which the event occurred.

Cause An internal error occurred in the ODBC/MX service.

Effect The server is disabled.

Recovery Identify the problem server and stop it.

31002

Start ODBC/MX server failed on port port-number. Event Type: event-type Component: component Object Reference: object-reference

`port-number`	indicates the number of the port that failed.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The spawn process failed.

Effect The ODBC/MX server is not started.

Recovery Check for server and file-system problems and correct them.

31003

Stop ODBC/MX server failed on port port-number. Event Type: event-type Component: component Object Reference: object-reference

`port-number`	indicates the number of the port that failed.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service could not stop an ODBC/MX server because of a previous error.

Effect The ODBC/MX server is not stopped.

Recovery Check the ODBC/MX event log for the previous error.

31005

ODBC/MX data source data-source changed state from previous-state to current-state. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of the data source.
`previous-state`	indicates the state of the ODBC/MX service before the event occurred.
`current-state`	indicates the current state of the ODBC/MX service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause An internal error occurred for the specified ODBC/MX data source during a state change.

Effect The ODBC/MX data source might not be available for use by client applications.

Recovery Restart the ODBC/MX data source. Report this problem to your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms.
Details from the message or messages generated.
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable.

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products.

31006

No more ports available to start ODBC/MX servers. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause All ports configured for ODBC/MX servers are in use, and the ODBC/MX service cannot start any more servers.

Effect The ODBC/MX server is not started.

Recovery The ODBC/MX server cannot start until a port is available. Use the NonStop Software Manager to determine the status of ODBC/MX servers. To free up additional ports, disconnect unused ODBC/MX clients and stop idle ODBC/MX servers.

31007

ODBC/MX service is started. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service is started.

Effect None.

Recovery Informational message only; no corrective action is needed.

31008

The ODBC/MX data source data-source is started. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service has started the specified data source.

Effect None.

Recovery Informational message only; no corrective action is needed.

31009

ODBC/MX service failed to start due to the previous error(s). Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service failed to start because of one or more errors.

Effect The ODBC/MX service is not started.

Recovery Check the ODBC/MX event log for the previous error(s) that occurred.

31010

ODBC/MX service started with some information. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service was able to spawn processes but with problems.

Effect The ODBC/MX service is started.

Recovery Check the ODBC/MX event log for the previous error(s) that occurred.

31011

Start ODBC/MX data source data-source failed. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The specified ODBC/MX data source failed to start because of one or more errors.

Effect None.

Recovery Check the ODBC/MX event log for the previous error(s) that occurred.

31012

The ODBC/MX data source data-source started with some information. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The specified ODBC/MX data source is started with some warnings.

Effect None.

Recovery Check the ODBC/MX event log for the previous error(s) that occurred.

31013

ODBC/MX service is stopped. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the ODBC/MX service.

Effect The ODBC/MX service is stopped.

Recovery Informational message only; no corrective action is needed. To use ODBC/MX again, you must restart it.

31014

The ODBC/MX data source data-source is stopped for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the specified ODBC/MX data source.

Effect The ODBC/MX data source is stopped and is not available for client connections.

Recovery Informational message only; no corrective action is needed.

31015

ODBC/MX service stopped for reason. Event Type: event-type Component: component Object Reference: object-reference

`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the ODBC/MX service, and some failures occurred.

Effect The ODBC/MX service is stopped.

Recovery Check the ODBC/MX event log for the previous error(s) that occurred.

31016

The ODBC/MX data source data-source stopped for reason with some information. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A stop request was issued to the specified ODBC/MX data source, and some warnings occurred.

Effect The ODBC/MX data source is stopped.

Recovery Check the ODBC/MX event log for the previous error(s) that occurred.

31017

Setting the initial ODBC/MX server context failed. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service could not set the initial context for the ODBC/MX server.

Effect The ODBC/MX server is not usable for client connections.

Recovery Stop the ODBC/MX server, correct the problem, and retry.

31018

ODBC/MX Server is started in debug mode. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX server is started in debug mode.

Effect None.

Recovery Informational message only; no corrective action is needed.

31019

ODBC/MX Server changing state from previous-state to current-state. Event Type: event-type Component: component Object Reference: object-reference

`previous-state`	indicates the state of the ODBC/MX service before the event occurred.
`current-state`	indicates the current state of the ODBC/MX service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The state of the ODBC/MX server has changed.

Effect The ODBC/MX server is in the specified state.

Recovery Informational message only; no corrective action is needed.

31020

The ODBC/MX data source data-source is stopping for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The Stop option was issued for the specified ODBC/MX data source.

Effect The data source is in the process of stopping gracefully and is not available for client connections.

Recovery Informational message only; no corrective action is needed.

31021

The ODBC/MX data source data-source is stopped abruptly for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Stop Abrupt option was issued for the specified ODBC/MX data source.

Effect The data source is stopped and is not available for client connections. The Stop Abrupt option stops a data source immediately, without waiting for its associated ODBC/MX servers to finish current SQL/MX statements or sessions. The Transaction Manager tries to roll back outstanding transactions. However, the database might be left in an inconsistent state.

Recovery Informational message only; no corrective action is needed.

31022

The ODBC/MX data source data-source stopped abruptly for reason with some information. Event Type: event-type Component: component Object Reference: object-reference

data-source	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The specified ODBC/MX data source was stopped abruptly with the Stop Abrupt option, and some failures occurred.

Recovery Check the ODBC/MX events in the application log for the previous error(s) that occurred.

31023

The ODBC/MX data source data-source is stopping abruptly for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The Stop Abrupt option was issued for the specified ODBC/MX data source

Effect The data source is in the process of stopping abruptly and is not available for client connections.

Recovery Informational message only; no corrective action is needed.

31024

The ODBC/MX data source data-source is stopping in Stop-When-Disconnected mode for reason. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The Stop option, with the Stop When Disconnected mode, was issued for the specified ODBC/MX data source.

Effect The data source is not stopped until all clients have disconnected. The data source rejects new connection requests.

Recovery Informational message only; no corrective action is needed.

31025

ODBC/MX service is stopped abruptly for reason. Event Type: event-type Component: component Object Reference: object-reference

`reason`	indicates the reason that accompanied the stop request.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A Stop Abrupt option was issued for the ODBC/MX service.

Effect The ODBC/MX service is in the process of stopping.

Recovery Informational message only; no corrective action is needed.

31026

ODBC/MX service started with warning warning-text from Configuration server. Event Type: event-type Component: component Object Reference: object-reference

`warning-text`	indicates the warning message returned by the configuration server.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service was started, but the ODBC/MX configuration server returned a warning.

Effect The ODBC/MX service is started.

Recovery Correct the problem indicated in the warning.

31028

SQL/MX has initialization successfully, ODBC/MX service cannot be started. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause A start request was sent to the ODBC/MX service, but the SQL/MX initialization, which includes the ODBC/MX initialization, has not completed.

Effect The ODBC/MX service is not started.

Recovery Wait for the SQL/MX and ODBC/MX initialization to complete, and then start the ODBC/MX service.

31029

ODBC/MX service is initialized. Event Type: event-type Component: component Object Reference: object-reference

`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service has finished initialization.

Effect None.

Recovery Informational message only; no corrective action is needed.

31030

ODBC/MX service failed to save data source data-source status status. Event Type: event-type Component: component Object Reference: object-reference

`data-source`	indicates the name of a data source.
`status`	indicates the status that could not be saved for the data source.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service could not save a status change for the indicated data source because of one or more errors.

Effect The ODBC/MX data source status change is not saved.

Recovery Check the application log for the errors that occurred, which most often are SQL/MX or network component errors. Correct the problem.

31031

ODBC/MX service failed to save status status of ODBC/MX service. Event Type: event-type Component: component Object Reference: object-reference

`status`	indicates the status that could not be saved for the ODBC/MX service.
`event-type`	indicates whether this event is a warning, an error, a critical error, or an informational message.
`component`	indicates the ODBC/MX component that reported the event.
`object-reference`	indicates the reference of the object in which the event occurred.

Cause The ODBC/MX service could not save a status change because of one or more errors.

Effect The ODBC/MX service status change is not saved.

Recovery Check the application log for the errors that occurred, which most often are SQL/MX or network component errors. Correct the problem.

31033

ODBC/MX server failed to write to collector-type collector due to error errnum Session ID: session-id Component Name: ODBC/MX Service Object Reference: object-reference Error Message: error-message Collector Name: alternate-collector-name

`collector-type`	indicates the type of collector, ODBC/MX server trace or resources statistics.
`errnum`	indicates a file system error.
`session-id`	indicates the unique session ID generated by the ODBC/MX server at the time the connection is established.
`object-reference`	indicates the reference of the object in which the event occurred.
`error-message`	is text explaining the error encountered.
`alternate-collector-name`	is the name of the alternate collector started for resource statistics or server trace.

Cause An alternate collector, specified in the MXOAS command for resource statistics or server trace, is not running, or the name is invalid.

Effect ODBC/MX server cannot write to the named collector.

Recovery If the alternate collector is not running, stop and start another trace or statistics collector. If the collector name specified in the MXOAS command is invalid, stop the ODBC/MX service and reissue the MXOAS command with a valid collector name.

31034

ODBC/MX Trace: Session ID: session-id Function: Enterfunction Sequence Number: sequence-number function-input-parameters OR Session ID: session-id Function: Exitfunction Sequence Number: sequence-number function-exit-parameters

`session-id`	indicates the unique session ID generated by the ODBC/MX server at the time the connection is established.
`function`	indicates the ODBC/MX server function that is being traced.
`sequence-number`	indicates which part of the message you are viewing. Messages too large for one message template are divided into smaller messages. The sequence number is 0 for the first or only part of a message and 1 for additional parts, if any.
`function-input-parameters`	is the list of input parameters to the function.
`function-exit-parameters`	is the list of output parameters from the function.

Cause A trace informational message was issued.

Effect None.

Recovery Informational message only, no corrective action is needed.

31035

ODBC/MX Statistics: Session ID: session-id Message Attribute: message-attribute Sequence Number:sequence-number Message Info:statistics-information message-attribute is: { SESSION:ConnectionInformation } { SESSION: SessionSummary } { STATEMENT: SQLStatement } { STATEMENT: SQLExecDirect } { STATEMENT: SQLExecute } { STATEMENT: SQLPrepare } { STATEMENT: SQLFetch }

`session-id`	indicates the unique session ID generated by the ODBC/MX server at the time the connection is established.
`message-attribute`	is the name of the statistics option you selected.
`sequence-number`	indicates which part of the message you are viewing. Messages too large for one message template are divided into smaller messages. The sequence number is 0 for the first or only part of a message and 1 for additional parts, if any.
`statistics-information`	indicates the statistics collected for the session or statement options selected.

Cause A resource statistics informational message was issued.

Effect None.

Recovery Informational message only; no corrective action is needed.