Purpose
The SessionOptions parcel sets various options for a session.
Parcel Data
The following table lists field information for the SessionOptions parcel.
Flavor Field | Parcel Body Length | Parcel Body Fields | ||
---|---|---|---|---|
114 | 10 |
|
|
Field Notes
Semantics specifies the semantics to be used for requests within a transaction.
Valid settings are:
Setting | Description |
---|---|
D | Default semantics |
T | Teradata semantics |
A | ANSI semantics |
Mode indicates that the system is in non-2PC Mode.
Two-phase commit is available only for Teradata Database for UNIX version 2 release 2 (or later), and for Teradata DBS for TOS version 1 release 5 (or later).
The valid settings are as follows:
Setting | Description |
---|---|
2 | Two-phase commit (2PC) mode. |
N | Non-2PC Mode. |
Conformance specifies whether or not SQL requests are to be checked for conformance with a particular language definition.
Valid settings are as follows:
Setting | Description |
---|---|
N | No conformance. |
2 | ANSI entry-level (FIPS 127-2). |
3 | ANSI intermediate-level (FIPS 127-3). FIPS 127-3 conformance is not supported by the Teradata Database for UNIX release 2.0.
|
utilityWorkload specifies whether or not the proprietary CHECK WORKLOAD statement will be used.
Setting | Description |
---|---|
0 | Proprietary CHECK WORKLOAD statement will not be used. |
1 | Proprietary CHECK WORKLOAD statement will be used. |
Redrive enable/disable the Automatic Redrive and Recoverable Network Protocol (RNP) features.
The valid settings are as follows:
Setting | Description |
---|---|
Y | To enable RNP and Automatic-redrive |
N | To enable RNP and disable Automatic-redrive |
E | To disable RNP and Automatic-redrive |
D | To enable RNP and use the Teradata Database setting for Automatic-redrive |
extendedLoadUsage can specify if the traditional or extended Multiload protocol will be used.
The valid settings are as follows:
Setting | Description |
---|---|
Y | It is available for the extended MultiLoad protocol. |
N | It is not available for the extended MultiLoad protocol. |
A | It is available for the extended MultiLoad protocol and it does not support the traditional MultiLoad protocol. |
0 | It is not available for the extended MultiLoad protocol for previous version (14.10) client. |
2 | It supports MLOADX Phase 2. |
B | It supports MLOADX Phase 2 and it does not support the traditional MultiLoad protocol. |