Statement-status - Call-Level Interface Version 2

Teradata Call-Level Interface Version 2 Reference for Mainframe-Attached Systems

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-07
dita:mapPath
jen1488824663137.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2417
lifecycle
previous
Product Category
Teradata Tools and Utilities

Statement-status specifies whether the Teradata Database may return Statement Status parcels instead of Success or OK parcels. Even if Statement-status is specified as 'D' or 'E', the Teradata Database may, at its discretion, return Success and OK parcels so the application should be prepared to handle either parcel.

In this language... The variable name for Statement-status is...
COBOL DBCNISS
PL/I DBCNISS
C, C++ dbcniSS
IBM Assembler DBCNISS
This routine... Does this for Statement-status. . .
DBCHINI writes
DBCHCL Reads (CON, IRQ, IWPF)
Statement-status is used by... To...
applications write
If StatementStatus... Statement-status to
indicates that Success or OK parcels are returned 'O'
indicates that StatementStatus parcels may be returned 'E'
indicates that StatementStatus parcels may be returned along with any optional description extensions 'D'
Unless a new application must support old versions of the Teradata Database, which would reject its use, Statement-status should always be set to 'E'. The CLIv2 Query routine QEPIESS (or QEPIASL) can be used to ascertain if the Database supports this enhancement.

Use mnemonics for the codes. Mnemonics are provided in the language definition file for the DBCAREA.