(B)0[m[4mSTART_SEGMENTED_STRING[m qwqqqqqqqqqqqqqqqqqqq>qqqqqqqqqqqqqqqqqwqk
mq> ( q> [4mTRANSACTION_HANDLE[m var q> ) qj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mq> ss-handle q> [4mUSING[m qwqqqqq>qqqqqqqqqwqq> context-var q> [4mIN[m qk
mqq> on-error qqj x
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqq<qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
mq> ss-field qqq>
1 – TRANSACTION_HANDLE
A keyword followed by a host language variable. A transaction
handle identifies each instance of a transaction. If you do not
declare the transaction handle explicitly, Oracle Rdb attaches an
internal identifier to the transaction.
If you start a transaction with a transaction handle, you must
include that handle in the START_SEGMENTED_STRING statement,
otherwise you get the following error:
RDB-E-EXCESS_TRANS, exceeded limit of !UL transactions !%S per
database attachment
In Callable RDO, use !VAL as a marker for host language
variables.
You can put parentheses around the host language variable name.
Normally, you do not need to use this argument. The ability to
declare a transaction handle is provided for compatibility with
other database products and future releases of Oracle Rdb.
2 – ss-handle
A host language variable or name used to refer to the segmented
string.
3 – on-error
The ON ERROR clause, which specifies host language statements or
Oracle Rdb data manipulation statements to be performed if an Oracle Rdb
error occurs. For more information, request HELP on ON_ERROR.
4 – context-var
A valid context variable. You use this context variable to
qualify the segments in the data manipulation statements that
follow.
5 – ss-field
A qualified field name that refers to a field defined with the
segmented string data type. Note that this field name must
be qualified by its own context variable. This second context
variable must match the variable declared in the START_STREAM
statement.