MX 3.x)

ODBC/MX Conformance

HP NonStop Open System Services ODBC/MX Client Driver—640328-001

3-14

Stored Procedures

ODBC/MX supports stored procedures, with the following exceptions:

•

ODBC/MP stored procedures cannot be converted to ODBC/MX procedures. They

must be rewritten.

•

Results sets, pointers to cursors, and returning codes are not supported.

For more information about stored procedures, see the SQL/MX Guide to Stored

Procedures in Java.

Transactions and Cursor Behavior with Multiple Statements

Timestamp Values with Fraction

If a value of the SQLFractionValue property is not specified in the ODBCDSN file (or if

it is equal to SYSTEM_DEFAULT or another value different from 9) and when a

timestamp struct value is inserted from a C/C++ program into a column with type time

or timestamp, the fraction field in the timestamp struct is considered in microseconds.

Table 3-20 lists the sample values that can be inserted from a C/C++ program into the

required column type and their corresponding expected values in microsecond.

Table 3-19. Transactions and Cursor Behavior

Autocommit SQL/MX Behavior Action Required

ON When any open statement reaches

end of data or end of cursor,

SQL/MX closes all other open

statements.

N.A.

OFF N.A. The application must explicitly

rollback or commit the transaction.

All open statements are closed at

that time.

Table 3-20. Sample Values Inserted From a C/C++ Program and Their

Corresponding Expected Values in Microsecond (page 1 of 2)

Value Specified in the

Fraction of the Client

Program Column Type

Expected Value in the

Column of the SQL/MX

Table

987654 timestamp(6) or time(6) 0.987654

87654 timestamp(6) or time(6) 0.087654

7654 timestamp(6) or time(6) 0.007654

654 timestamp(6) or time(6) 0.000654

54 timestamp(6) or time(6) 0.000054