Statement-status specifies whether or not the server may return StatementStatus parcels rather than Success or OK or Error or ErrorInformation or Failure or StatementError parcels.
|DBCHCL||reads (RCON, IRQ, IWPF)|
|Used by||Action Taken|
One of the following values may be set before establishing a connection:
Use mnemonics, which are provided in the language definition file for the DBCAREA, for the codes.
The total solution will also address various multi-error responses and the error texts for them. Teradata cannot produce the total solution in the Teradata Database 14.10 release. So, we will produce the solution in stages. Teradata Client and database products are finalized at different times. Therefore, the TTU 14.10 Client files describe some functionality that is not available in Teradata Database 14.10 database. Teradata will manage this by having a set of ESS levels for the new functionality. The first level will coincide with TTU 14.10 Client (less any non-database-implemented features) and Teradata Database 14.10 database. A new StatementStatus Parcel is being issued by the database. It, in first-level ESS, will only be sent to Client in replacement of Success or OK Parcels. It will only be sent on a session if the Client requests ESS responses in its SessionOptions parcel during logon.
However, the database reserves the right to send Success-or-OK in some cases, even if Client has asked for StatementStatus. The new StatementStatus Parcel is allowed to have extensions. Client applications should ignore any extensions that they do not recognize.
A setting of 'E' (for Enhanced) indicates the application desires ESS for the life of the session. A setting of 'D' (for Description) is the same as 'E' but also indicates that optional description extensions are desired. None of the description extensions have been implemented in TTU 14.10. So, there is no difference between 'D' and 'E' in TTU 14.10.