SQL/MX Glossary

Glossary
HP NonStop SQL/MX Glossary—523732-002
Glossary-23
nonsensitive command.
nonsensitive command. A SQL/MX connectivity service (MXCS) administrative command
that returns only the status or attributes of objects in the MXCS subsystem being
administered. Contrast with sensitive command.
NonStop Data Access Manager. See Data Access Manager (DAM).
NonStop ODBC driver. A Microsoft ODBC component needed for an ODBC application to
communicate with a server. ODBC drivers are DLLs and are loaded on demand.
NonStop ODBC/MX. A NonStop software product that allows client applications developed
for the ODBC application programming interface (API) to access an SQL/MX database
in an HP NonStop system running SQL/MX.
NonStop ODBC/MX association server. The ODBC/MX component that starts and
manages the ODBC/MX servers in HP NonStop systems and associates an ODBC
client with a specific ODBC/MX server.
NonStop ODBC/MX automatic startup option. An ODBC/MX startup option that causes
an ODBC/MX data source to be started automatically when the ODBC/MX service is
started. See also NonStop ODBC/MX manual startup option.
NonStop ODBC/MX configuration server. The ODBC/MX component that manages the
ODBC/MX configuration data in the system catalog schema.
NonStop ODBC/MX default data source. A data source named TDM_Default_DataSource
that ODBC/MX automatically creates in an HP NonStop system. ODBC clients can
connect to TDM_Default_DataSource and use ODBC/MX without having to add and
configure an ODBC/MX server data source on the NonStop system.
NonStop ODBC/MX driver. The ODBC/MX component that implements ODBC function
calls to enable an ODBC client application to access an SQL/MP database through an
SQL/MX server.
NonStop ODBC/MX governing action. The action taken by ODBC/MX when the limit is
exceeded for a resource management policy attribute. Examples of governing actions
are COMMIT and ROLLBACK.
NonStop ODBC/MX governing attribute. A resource management policy entity that is
used to compare an aspect of an SQL/MX query to a limit value. An example of a
governing attribute is the estimated cost of a query.
NonStop ODBC/MX manual startup option. An ODBC/MX startup option that requires the
user to manually start an ODBC/MX data source. See also NonStop ODBC/MX
automatic startup option.
NonStop ODBC/MX resource management policy. An attribute-value pair that associates
a governing attribute name with a test limit value and a governing action that
ODBC/MX takes if the limit value is exceeded.