SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Considerations for upgrading to SQL/MX Release
3.0
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
2-10
Using the read-only transaction access mode
*** ERROR[8402] A string overflow occurred during the evaluation of a
character
expression. Conversion of Source Type:DECIMAL SIGNED(REC_DECIMAL_LSE) Source
Val
ue:0x2B0001050204010507080705030203080803060502070906080209090706050207090608
04
to Target Type:CHAR(REC_BYTE_F_ASCII).
--- 1 row(s) selected.
>>
>>update tnumeric set a = a + a where cast( a * 20 as char (10)) > '5';
*** ERROR[8402] A string overflow occurred during the evaluation of a
character
expression. Conversion of Source Type:DECIMAL SIGNED(REC_DECIMAL_LSE) Source
Val
ue:0x2B0002040609010305070800020406090103050600 to Target
Type:CHAR(REC_BYTE_F_A
SCII).
--- 0 row(s) updated.
>>
Using the read-only transaction access mode
SQL/MX provides two transaction access modes namely read-only and read-write. In
the read-only access mode, you can only execute the SELECT statement. When you
migrate from SQL/MX Release 2.x to SQL/MX Release 3.x, applications using the
read-only transaction access mode might return SQL error 8551 along with file system
error 757.
The following set of operations demonstrate the error scenario for ODBC or JDBC T4
applications, MXCI, and embedded SQL programs:

The transaction access mode is set to read-only by either setting the read-
only connection attribute to TRUE, or by executing the SET
TRANSACTION READ ONLY statement.

A SELECT statement is prepared.

The transaction access mode is then changed to read-write. The
transaction access mode is set to read-write by setting the read-only
connection attribute to FALSE, or by executing the SET TRANSACTION
READ WRITE statement.