15.10 - Statement-status - Call-Level Interface Version 2

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

prodname
Call-Level Interface Version 2
vrm_release
15.10
category
Programming Reference
featnum
B035-2417-035K

Statement‑status specifies whether the server 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

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­­'

Note: 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 server supports this enhancement.

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